HTTP/1.0 500 Internal Server Error Connection

[Scyto]

I get this sometime when i connect to my nodelink pi, i have to refresh a few times or sometime reboot the pi if that doesn't work.

Happens from a few browsers.

 

HTTP/1.0 500 Internal Server Error Connection: close

Error: Operation is not valid due to the current state of the object

 

[Scyto]

i turned on logging to text file - this is all the log says related to the 500 error:

 

2017-12-06 17:34:12 - Web Request: /

 

I am on a older version of mono if that could be an issue?

[larryllix]

i turned on logging to text file - this is all the log says related to the 500 error:

 

2017-12-06 17:34:12 - Web Request: /

 

I am on a older version of mono if that could be an issue?

The 500 is because you have a huge log file making  NodeLink to tie up the CPU so badly that it can't answer a browser  connection you are attempting right then. Just hit refresh a few seconds later.

 

I get it with a RPi3 with mono 5.12? also.

 

Turn off your verbose  and recording and then reboot NodeLink

[Scyto]

The 500 is because you have a huge log file making  NodeLink to tie up the CPU so badly that it can't answer a browser  connection you are attempting right then. Just hit refresh a few seconds later.

 

I get it with a RPi3 with mono 5.12? also.

 

Turn off your verbose  and recording and then reboot NodeLink

i turned it on BECAUSE  i was getting 500 errors with it off....

My mono is latest via apt-get but is old: Mono version: 3.2.8 (Debian 3.2.8+dfsg-4+rpi1) 

[io_guy]

Yea in the next version I'm going to limit the web log to 200 entries.  These little processors chug pretty bad on 1000 (since some of them could be full http pages of data).

 

And yes, get a decent mono version.

[Scyto]

Yea in the next version I'm going to limit the web log to 200 entries.  These little processors chug pretty bad on 1000 (since some of them could be full http pages of data).

 

And yes, get a decent mono version.

I got the latest that apt-get upgrade had today, version didn't change : Mono version: 3.2.8 (Debian 3.2.8+dfsg-4+rpi1) is this ok?

[io_guy]

Not really but it's a Pi1 so there's not much to do.

 

My advice is throw $35 into a Pi3 and install the latest Raspbian per my howto.

[Scyto]

I found this, will give it a go before i port the whole thing over to a pi3 (the current pi is a 2b not a 1)

 

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF

 

echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list

 

sudo apt-get update && apt-get upgrade sudo apt-get install mono-complete

[io_guy]

Don't go to a 3 then, 2B is just as powerful.

[Scyto]

well that broke my mono install, i hate linux, dependency hell is way worse than DLL hell, guess moving to later version of the OS is good weeknd project.

 

I found this, will give it a go before i port the whole thing over to a pi3 (the current pi is a 2b not a 1)

 

yeah that did not work

[Scyto]

quick question why do you install more than just mono-runtime? also what is dirmngr?

[larryllix]

I found this, will give it a go before i port the whole thing over to a pi3 (the current pi is a 2b not a 1)

 

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF

 

echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list

 

sudo apt-get update && apt-get upgrade sudo apt-get install mono-complete

IIRC This will do it all and upgrade what you have now.

 

sudo apt-get update

sudo apt-get upgrade

[Scyto]

IIRC This will do it all and upgrade what you have now.

 

sudo apt-get update

sudo apt-get upgrade

Nope most definitely did not work. Dependency issues, I backed out the mono installs and tried several of the wheezy repos, all had issues. I just ran up a new stretch SD card and in middle of copying across my various HA apps.

[io_guy]

quick question why do you install more than just mono-runtime? also what is dirmngr?

Because the way they package the runtime does not include all the methods required.

 

Dirmngr is needed to handle the various key calls to setup the custom mono location for apt-get. For some reason the latest Raspbians dont include it by default.

[larryllix]

Nope most definitely did not work. Dependency issues, I backed out the mono installs and tried several of the wheezy repos, all had issues. I just ran up a new stretch SD card and in middle of copying across my various HA apps.

I found mono v5.x would not install on my RPi 1 due to missing system modules. The same distro install on my Rpi 3 went just fine.

I had found a way to force earlier versions of mono but then jumped ship tp RPi 3. It helped somewhat with errors.

 

It seems once a device starts giving errors with NodeLink it can escalate into all my devices until a reboot is done. This is rare but has happenned a few times..

[io_guy]

And it'll keep happening without a log file.

[Scyto]

And it'll keep happening without a log file.

good to know, thanks

I updated to stretch and latest mono too

[Scyto]

Yea in the next version I'm going to limit the web log to 200 entries.  These little processors chug pretty bad on 1000 (since some of them could be full http pages of data).

 

 

how about two log panes - one for key events like the startup and critical errors that mighght need too be kept / are infrequent and the other pane a rotating for all those gem/dsc/isy events that don't need to be kept over time and is suspect are causing the bloat....  (or just make the startup events an info page, not a log at all?)

[io_guy]

The few startup items don't make a difference.

 

If you need the log for debug just save files. No performance issue with them.

[larryllix]

And it'll keep happening without a log file.

I wasn't sure whether you were addressing my post or not.

Are you are saying without the log file option enabled, nodelink will eventually kick out errors? I have never used it enabled.

Can you elaborate on that please?

 

 

Also..

is a new NodeLink log file created each day (I noticed the date incorporated into the filename), or is it continuous forever, or is there some length management?

[io_guy]

New each day.

 

I was saying i can't do anything with "it stopped working and broke" or "network went down and nodelink seemed unhappy". I need logs.

[larryllix]

New each day.

 

I was saying i can't do anything with "it stopped working and broke" or "network went down and nodelink seemed unhappy". I need logs.

It sounded like lack of a log file could escalate it. LOL

 

OK. so recommended to turn on log file option just for those rare times when some quirk happens.

Nice the logs are broken down into days. When I first loaded my ISY logs it took almost an hour to load into an editor.

 

Thanks!

[Scyto]

 

Are you are saying without the log file option enabled, nodelink will eventually kick out errors? I have never used it enabled.

Can you elaborate on that please?

 

 

yes it is to do with the number of log eitems held to display, it happens on my  stretch+latest mono too.

it is ok now i know that it is doing that, i can work around it

[larryllix]

yes it is to do with the number of log eitems held to display, it happens on my  stretch+latest mono too.

it is ok now i know that it is doing that, i can work around it

I think we have some real cross posting confusion here. LOL

 

This is the way I interpreted it.

The log comment from io_guy was to me regarding my lack of producing logs to troubleshoot with.

I misread that and asked for clarification as it sounded like the  log option had something to do with creating the errors.

 

Note: The log is not the verbose modes but rather a file created to log communications and should not cause any 500 errors. The verbose mode will because every time you login to Nodelink it has to show you the visual list with thousands of lines, causing it to not respond quick enough to your browser.

[Scyto]

Yes you are confused.

 

The only point I made is the 500 internal server error occurs even when verbose logging is turned off and log to file is turned off. io-guy has confirmed this, you seem to keep wanting to argue this point or think I have missed some basic noob setting. I have no idea why!