7.5.00095 - Release Notes

billcreager2 · 2016-12-19T12:57:58.000Z

7.5.00095

Help Desk

85083 - app login fails when frontend is intermittently available
83251 - Help desk no longer auto-refreshing ticket view
83021 - orange status bubble does not appear for updated tickets in IE11

Platform

78095 - Update OpenSSL to version 1.0.2j
74732 - Current Apache version (2.2.29) vulnerable to CVE-2015-3183

Download the latest version here: www.spiceworks.com/download

erik · 2016-12-19T13:14:05.000Z

It feels like a long time since the last update!

edwin10dam · 2016-12-19T13:24:38.000Z

ErikN:

It feels like a long time since the last update!

Finally …

friesenj · 2016-12-19T13:29:34.000Z

Same way thinking it’s been a long time since an update came out…

porkyp · 2016-12-19T13:44:10.000Z

Thanks for fixing the auto-refresh issue.

Robert762 · 2016-12-19T13:47:15.000Z

Grabbed this update last night during a scheduled maintenance window - great timing!

briansteingraber · 2016-12-19T13:57:42.000Z

Not a lot of fixes, but they are all goodies!

cynthia1118 · 2016-12-19T14:04:40.000Z

Thanks for continuing to make free even better!

vhscarpacci · 2016-12-19T16:03:14.000Z

Why is there so many updates? Do it once do it right see you next year.

jimgall2 · 2016-12-19T16:24:42.000Z

Is there a public-facing bugtracker for the software? Listing the bug number id’s only makes sense if we can follow the development of the bugs/solution.

billcreager2 · 2016-12-19T16:28:46.000Z

jgdaqs:

Is there a public-facing bugtracker for the software? Listing the bug number id’s only makes sense if we can follow the development of the bugs/solution.

No public-facing bug tracker…and we probably never will. But, we put them in the release notes because there a various threads and support tickets/emails that will contain the bug number. This makes it easy for those folks that are waiting for a specific bug fix, as we tend to change the title of the bugs a lot

las · 2016-12-19T17:58:04.000Z

Such a long wait and so few fixes

93 was leaky and a CPU hog now there is an EXTRA Finder instance (3x) jumping from 200Mb to 302Mb RAM Just for finders that use about 13% each on quad core platform.

Spiceworks.exe at 5 to 19% CPU and 300Mb RAM

Two httpd instances at 35Mb RAM and 1 to 5% CPU currently

Well on the way to Bloatware if this is maintained.

Running for a bit, still monitoring …

UPDATE: 4th Finder just fired up at 13% CPU and 105Mb RAM extra resou.

billcreager2 · 2016-12-19T18:57:46.000Z

LAS:

Such a long wait and so few fixes

93 was leaky and a CPU hog now there is an EXTRA Finder instance (3x) jumping from 200Mb to 302Mb RAM Just for finders that use about 13% each on quad core platform.

Spiceworks.exe at 5 to 19% CPU and 300Mb RAM

Two httpd instances at 35Mb RAM and 1 to 5% CPU currently

Well on the way to Bloatware if this is maintained.

Running for a bit, still monitoring …

UPDATE: 4th Finder just fired up at 13% CPU and 105Mb RAM extra resou.

Hey LAS,

We didn’t make any changes to finder in this release, but sounds like there is something wacky going on with yours, as you shouldn’t be getting that many. Would you please open a support ticket (support@spiceworks.com), so we can get some logs and see if we can figure out what’s going on with your memory usage

Mike400 · 2016-12-20T01:02:54.000Z

Thanks for getting the intermittent connection to SW home servers fixed.

Mike400 · 2016-12-20T01:28:20.000Z

7.5.00095 installed and started in about half the time of 7.5.00093. Did you guys make some serious performance improvements?

vincedancer · 2016-12-20T09:05:07.000Z

Thanks for finally fixing the refresh problem :).

miguelsalgueiro · 2016-12-20T12:21:52.000Z

Good work, greetings from argentina!

billcreager2 · 2016-12-20T12:22:59.000Z

Mike400:

7.5.00095 installed and started in about half the time of 7.5.00093. Did you guys make some serious performance improvements?

No blatant performance improvements, but we did update Apache and OpenSSL, which might have some improvements backed in

niccrockett · 2016-12-20T13:52:21.000Z

I had an opposite reaction on my server.

I tried installing and it got stuck on the Starting Up splash screen. Progress bar got all the way to the end, but wouldn’t finish. I waited hours to see if it would go through.
Re-ran the installer and got the same results.
Ran the restore_spice.exe file to restore the previous backup. However, since I ran the installer twice it restored my first try of installing 7.5.00095.
Surprisingly it restored and will start-up. However it takes 20-30 minutes to start. I also don’t know if my install or database are ok.

I’ve already submitted a support ticket (293281) for this issue, but haven’t heard back from anyone yet.

I’m posting this here so people who might run into this issue don’t try the installer twice before restoring. I also wanted to remind people to backup before they install any Spiceworks update. I create a backup right before I do an install and move it out of the backup folder, plus I do nightly backups that are then backed up to another server. This has saved my Spiceworks install several times.

If I have anymore useful info I’ll post back to this thread.

Mike400 · 2016-12-20T14:22:30.000Z

NicCrockett:

I also wanted to remind people to backup before they install any Spiceworks update. I create a backup right before I do an install and move it out of the backup folder, plus I do nightly backups that are then backed up to another server. This has saved my Spiceworks install several times.

If I have anymore useful info I’ll post back to this thread.

As far as I’m concerned the Spiceworks installer should perform an standard backup and label it appropriately. I always do a backup immediately before and after I upgrade. The one after is to provide a baseline for the new version.