1

Hello,

Since yesterday at 10:30AM EST we are unable to load Spiceworks Desktop. We first lost communication with the server and had to reboot the server. However, since reboot, we were unable to launch SW desktop. It gets stuck at the Spiceworks is warming up/splash screen. We try to change the ports from 80/443 to 9675/9676 with no luck. We tried to launch the application in all browsers (IE, FF, Chrome) with no luck. We checked the logs and nothing stand out with the excepting that Spiceworks stopped and it did this 1 time before. But, there was nothing alarming within the logs. Try to run SW as a non-service and back as a service. SW is set run Automatically as a service. We did a rollback of Windows in case the issue was with Windows with no luck. We’re now attempting to upgrade to 7.2 but we’re stuck at the 95% (at the Spiceworks is updating your installation… Please give us a minute or two to get you set up.) updating progress. However, we notice that some apache service were being terminated at first but didn’t after the rollback. Furthermore, we have noticed that there may be some corrupt apache installation or postgre. Could this be the problem?

Details on our system: Win7Pro SP1, 8GB RAM, i5 processor

We have been down for 2 days now. Any assistance would be greatly appreciated. Thanks in advance.

1 Spice up
2

check the Production.log in the spiceworks\logs folder

Could be a bad DB and you’ll need to contact support@spiceworks.com to get them to fix up the DB.

1 Spice up
3

Ok, I’ve done and see nothing that stands out. I did email support earlier this morning and I’m awaiting their response.

However, I notice that within the Fatal log, I several timeouts awaiting for apache to start along with execution expired with several blocks.These blocks include block on lock shared, load known device, load excluseive, etc. There is even several an undefined method ‘bootstrap’ for #String:0x4b7d2bc’ could this be the problem as there are blocks and locks in loading the application initializers and settings. I assume this is where my issue lies, how can I correct this problem?

4

[SOLVED] FYI…The issue turned out to be a problem with the

settings file. For anyone facing a similar situation, you may follow my

steps to see if it correct the problem by backing up your DB files

first, removing and reinstall the program and then transferred in the DB

files and renaming c:\program files

(x86)\spiceworks\data\settings.yaml to settings.old and relaunch the

program.

Thanks to Support which was fast and friendly, we’re back up and