Spiceworks - Error 500 issue

[bodminman]

Hi there,

 

we have been plagued with this issue on and off for years and am about to start looking at other Helpdesk solutions.

 

However, before I do, I just thought I'd try here just in case someone has has a similar issue and has found a solution, that so far Spiceworks haven't been able to provide.

 

Basically, we have 5 separate queues for jobs and when it's all working it's great, but at the moment we are getting the 500 error every day or two and are having to restart the Spiceworks service to get things going. Not a massive issue but as I'm off site more and more at the moment, this means people cannot use it for several hours sometimes.

 

Spiceworks is on it's own dedicated PC which has Server 2012 installed on to a SSD with 16gb RAM. Spiceworks has always been run on a dedicated machine but we have moved OS several times to see if that resolves the issue but it hasn't.

 

Lately, Spiceworks are saying that a particular IP is hitting the app all day. This particular IP is the Helpdesk itself that is logged in to Spiceworks all day to deal with tickets. Isn't this supposed to be what it's designed to do?

 

Banging my head against the wall with this one but if anyone has any sniff of info that could help then that would be greatly appreciated.

 

Thanks

[Steve21]

If you check your production logs under C:\Program Files (x86)\Spiceworks\log it should say why the 500 occurs.

 

Normally it's something like it took too long to process, 2s is the standard it looks at unless it changed.

 

An example from ours: I[02:32:17.74 bbce14] Completed in 2375ms (View: 0, DB: 47) | 500 Internal Server Error [http://localhost/dataloader/persist_warranty_data] which as you can see took 2.3s as the pool limits got hit, but these can be increased if it's that

 

When you say using the App do you mean the apps within spicework? Normally you'd be using the web browser to access it for new versions, as the "real" apps aren't always updated in line with the main releases

 

Steve

[bodminman]

@Steve21

 

thanks for that.

 

This keeps appearing:

 

Status: 500 Internal Server Error

could not obtain a database connection within 2 seconds. The max pool size is currently 40; consider increasing it.

 

Any idea as to what the pool size is and how to increase it?

 

We current have environment variable SQLITE_DB_POOL set to 120 as resquest by SW support.

 

Thanks

[Steve21]

Unless it's changed 100 was the max I think. There's also an option within Spiceworks to change it now too, under settings -> global -> advanced -> Global thread pool

 

If it's showing as 40 in the log that 120 isn't working it seems (Unless that's the old line before you changed it?), so would advise trying 100 on both sides (environment wise and spice side). Also don't forget you need to reboot whole server for those to apply.

 

Steve

[bodminman]

Unless it's changed 100 was the max I think. There's also an option within Spiceworks to change it now too, under settings -> global -> advanced -> Global thread pool

 

If it's showing as 40 in the log that 120 isn't working it seems (Unless that's the old line before you changed it?), so would advise trying 100 on both sides (environment wise and spice side). Also don't forget you need to reboot whole server for those to apply.

 

Steve

 

Cheers.

 

In the SW Global bit it was showing 100. They have 25, 50, 100, 200 and 300 as options. I have changed it to 200 on both side and will see if that helps.

 

Will report back in a day or so.

 

Thanks @Steve21

[Steve21]

Just to confirm (Sure you are but might be worth checking), Don't forget a) make sure it's the system var, not user var it's been set for, and b) give it a whole kick

 

Hopefully that'll solve it, but again might just be worth checking the logs and seeing if it does appear as even if you get another 500 error the message should change to something like max pool is currently 200 etc, else there's another problem

 

Steve

[bodminman]

Just thought I'd report back.

 

We have now had a stable Spiceworks for 6 days. This is the first time in months it has been running for more than 24hrs without the dreaded 500 error.

 

Thanks for your help @Steve21

[Steve21]

Good to hear! Lets hope it stays that way!

 

Steve