ArchiveSW - Display & Data Archive Storage

I think this new bug has been fixed.

1 Like

Boy. You just found three issues I forget to account for on new installations.

Get this file and run it from the wfarchve folder:

wget -N http://fsoft.com/wfarchive/fix.js

That will solve the unknown columns.

On the Panel, Look in Process Management and see if it is running.

Good evening from Colorado.

I have pushed out a lot of changes that undo the changes from last week. I removed the internal UDP communications and added TCP communications.

The Server process will act as the TCP server and the other process applications act like clients. This allows for more flexibility and more expansion.

As usual, please report any issues and I will correct them ASAP. I appreciate the support.

5 Likes

Many thanks - will report any further issues.

Not too bothered with the panel at present - really want the full database for use with my own web display currently used for my Davis system

1 Like

One goal is to make the data stored easy to use and share. If there is anything I can write to make this work for you please let me know.

I am still considering broadcasting some data via UDP but so far I havenā€™t had the need.

2 Likes

@GaryFunk

I updated yesterday and again this am.

Couple unknown fields in DailyStats.log
Ran alterfiles but gets stuck.
Read through all above, short on time right now but will look for a solution in previous posts.

2018-10-08 07:00:04 MariaDB connected
2018-10-08 07:00:05 Error(s2): ER_BAD_FIELD_ERROR: Unknown column ā€˜tempHā€™ in ā€˜field listā€™
2018-10-08 07:00:08 Error(s4): ER_BAD_FIELD_ERROR: Unknown column ā€˜illuHā€™ in ā€˜field listā€™

1 Like

Run fix.js. You will find the link in previous messages.

1 Like

Ok. done. I knew I saw that info earlier.

Thx.

1 Like

Panel issue appears to be:
Error: Cannot find module ā€˜socket.ioā€™
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/home/pi/wfarchive/panel.js:100:10)
at Module._compile (module.js:653:30)
at Object.Module._extensionsā€¦js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)

1 Like

Well, I will check to see why on my end.

At the wfarchive folder, run

npm install socket.io --save

1 Like

That did the trick!

FYI - I did a complete re-install (manually) and the panel issue was the only one!

Phil

1 Like

Okay. I will check the instructions on the manual install. Thank you.

1 Like

Very good, ran into this problem this am.
Will do this eve.

1 Like

I am working on a new feature that will help you see what is going on with your system.
Capture

You will now be able see some internal activity.

2 Likes

New files uploaded. More bugs found and fixed. Some small enhancements.

1 Like

I did when coming home and had to restart via terminal, the process tab gave an error

ReferenceError: /home/eric/wfarchive/views/process.ejs:4
    2| <!DOCTYPE html>
    3| <% var page = 'process'; %>
 >> 4| <% if ('refresh' in q) { %>
    5| <script>
    6| setTimeout(function() {
    7| 	location.assign("/process");

q is not defined
    at eval (eval at compile (/home/eric/wfarchive/node_modules/ejs/lib/ejs.js:618:12), <anonymous>:14:25)
    at returnedFn (/home/eric/wfarchive/node_modules/ejs/lib/ejs.js:653:17)
    at tryHandleCache (/home/eric/wfarchive/node_modules/ejs/lib/ejs.js:251:36)
    at View.exports.renderFile [as engine] (/home/eric/wfarchive/node_modules/ejs/lib/ejs.js:482:10)
    at View.render (/home/eric/wfarchive/node_modules/express/lib/view.js:135:8)
    at tryRender (/home/eric/wfarchive/node_modules/express/lib/application.js:640:10)
    at Function.render (/home/eric/wfarchive/node_modules/express/lib/application.js:592:3)
    at ServerResponse.render (/home/eric/wfarchive/node_modules/express/lib/response.js:1008:7)
    at /home/eric/wfarchive/server.js:372:8
    at /home/eric/wfarchive/node_modules/pm2/lib/API.js:591:19
1 Like

Did you download and restart server.js?

I used the online update link, and when I wanted to go to the process page, I got the above mentioned error, so terminal and the good old pm2 restart all, problem solved (for now)

2 Likes

Thatā€™s interesting. If it happens again let me know.

1 Like

Thank you for you work! Just what I was looking for. Canā€™t wait for the next ā€œupgradeā€ :slight_smile:
Iā€™ll be running the panel in all rooms via wall mounted tablets
Great Job!

2 Likes