File Name Unknown - Error Message

[King Kong]

Hello
Again I apologize if I'm posting this to the wrong forum.

Error message = "File Name Unknown"
Oregon Scientific WRM 100
BeagleBone Black
Debian
See attached files from MXdiags

Thanks

[BigOkie]

Hello
Again I apologize if I'm posting this to the wrong forum.

Error message = "File Name Unknown"
Oregon Scientific WRM 100
BeagleBone Black
Debian
See attached files from MXdiags

Thanks

It almost looks like you're running more than one instance of Cumulus (in this case I'm guessing you would be running more than one instance of mono). You might look to see.

[King Kong]

Hello
Thanks for the help. I'm relatively new to Linux and so had to find out how to display individual processes. Please see attached file. I hope I've got the correct information.
Note: after originally posting the attached screen shot, I found out that I could scroll the screen. Rookie mistake. However I didn't see a "mono" process. Next I did a "pgrep mono" which is suppose to list the process ID of all currently running processes. No information was returned therefore I'm concluding that "mono" isn't running. Is this assumption correct or is there another Debian command that I should be using to verify if the "mono' process is running?

Thanks

[BigOkie]

Hello
Thanks for the help. I'm relatively new to Linux and so had to find out how to display individual processes. Please see attached file. I hope I've got the correct information.
Note: after originally posting the attached screen shot, I found out that I could scroll the screen. Rookie mistake. However I didn't see a "mono" process. Next I did a "pgrep mono" which is suppose to list the process ID of all currently running processes. No information was returned therefore I'm concluding that "mono" isn't running. Is this assumption correct or is there another Debian command that I should be using to verify if the "mono' process is running?

Thanks

Try issuing this command instead and post the results:

ps -ax | grep mono

[King Kong]

Hello
I tried the command:
ps -ax | grep mono

and the "kill" command. I don't think I stopped the mono process nor am I sure that it was running in the first place. Please see attached screen shot.

Thanks for the help and do you have any other suggestions?

[BigOkie]

Hello
I tried the command:
ps -ax | grep mono

and the "kill" command. I don't think I stopped the mono process nor am I sure that it was running in the first place. Please see attached screen shot.

Thanks for the help and do you have any other suggestions?

It wasn't. Do you have mono installed?

Type in 'which mono' and give the response.

I mean , I assume you are since you're giving me log files.

[freddie]

Hello
I tried the command:
ps -ax | grep mono

Your syntax is incorrect - it should be:

Code: Select all

ps ax | grep mono

i.e no "-" needed before the "ax".

and the "kill" command. I don't think I stopped the mono process nor am I sure that it was running in the first place.

The process you were attempting to kill was your search for "mono" which would've terminated by the time you got round to typing the kill command. To remove the search processes from the results returned by grep, use the following:

Code: Select all

ps ax | grep mono | grep -v grep

This will specifically exclude anything with the word "grep" from the results returned by the command.

[King Kong]

Hello
It looks like I have mono installed. Please see screen shot.

Thanks

[rogerthn]

Hello
It looks like I have mono installed...

To see what version

Code: Select all

mono -V

[King Kong]

Hello
The Mono version is 3.8.0. Should I be updating to a newer version?

[steve]

It's not able to find your station. What is the output from the command lsusb? Do you have packages mono-complete and libudev0 installed? Cumulus needs libudev.so.0, as mentioned in the instructions.

[King Kong]

Hello Steve

Thanks for the help. I can confirm the "mono" is installed (but not "mono-complete"). Also "libudev0:armhf is installed. Please see attached files.

Thanks for the "lsusb" command. This helped me clue into something; my weather station wasn't plugged into the BeagleBone. In my defense the instructions don't mention anything about connecting the weather station to the device and then configuring it. Maybe it would be a good idea to add that in the configuration notes. Just a suggestion. I had my weather station running on a Windows machine and wanted to configure the BeagleBone "off line" before moving the hardware over to it. Once the weather station was had, CumulusMX started and I was able to configure it.

The original issue seems to be resolved unless you advise me of a difference between "mono" and 'mono-complete" and I need to replace one with the other.

My new issue is the web pages seem to hang. No information is being displayed on the dashboard and I've stopped reporting to Wunderground. The auxiliary display (the piece of equipment that came from Oregon Scientific) is displaying the temperature and wind speed so I know the outdoor sensors are being red.

You you like me to post this in a new post?

[steve]

My new issue is the web pages seem to hang. No information is being displayed on the dashboard

What browser are you using? Are any errors displayed in the F12 developer console in the browser?

and I've stopped reporting to Wunderground.

Are you using rapid fire? If so, turn that off and see if it starts updating. Turn on debug logging and after a WU update should have taken place, zip up the MX diags folder and attach it to a reply in this thread.

[King Kong]

My new issue is the web pages seem to hang. No information is being displayed on the dashboard

What browser are you using? Are any errors displayed in the F12 developer console in the browser?
I'm using IE, Chrome + FireFox. All with the same results.
F12 =
Using //@ to indicate sourceMappingURL pragmas is deprecated. Use //# instead jquery-latest.min.js:1:0
Use of getPreventDefault() is deprecated. Use defaultPrevented instead.

I hope that's what your looking for. From the main html page I pressed "F12" and did a copy of the information.

and I've stopped reporting to Wunderground.

Are you using rapid fire? If so, turn that off and see if it starts updating.
Not using "Rapid Fire"

Turn on debug logging and after a WU update should have taken place, zip up the MX diags folder and attach it to a reply in this thread.

Stopped CululusMX
Added "Logging=1" to the "Station" section on the "Cumulus.ini" file.
Started CumulusMX

[steve]

There may be an issue with the port used for the web socket data (8002), and something isn't allowing communication on that port. If you view a page that doesn't use web sockets, e.g. the today/yesterday page, do you see any data?

The WU problem is this:

WU Response: OK: INVALIDPASSWORDID|Password and/or id are incorrect