Dashboard Widget Problem (Multiple Service status items)
-
The only package that went AWOL is widescreen, but enough about that…
Well… I'm afraid the WS "package" is causing the whole issue for you here.
-
widescreen - Thats what I thought.
Try this. Make sure you delete widescreen then Save your settings. Reinstall pfsense (wipe box). Reload settings.
I bet its good. I think doktornotor is right.
-
Sorry to say, but this (reinstalling) is not an option as it is a production system with 180 users…
Is there a way that I can uninstall/remove the widescreen package via the console?
cyber7-out
-
ps - pkg-info does not show anything for widescreen…
-
Ask the "package" author in the relevant thread. AFAIK this has been distributed as a tarball, plopping the additional theme on the disk, plus patching some system files so that the theme was recognized. At the risk of stating the obvious, why on earth are you sticking similar experimental stuff on a production box with hundreds of users?
-
You can knock this out in 3 minutes if you are good… 10 tops.
Then you won't have downtime again for a year.
(Well - I say that assuming you have a keyboard, VGA, CD ROM handy - If so, its fast)
-
Ok, this is what I did:
(Because I run on a VM)- Reverted to my snapshot before the upgrade and rebooted,
- Uninstalled (removed) widescreen, snort dashboard widget, lightsquid, mailreport, Notes, Open-VM-Tools, pfflowd,
- Reloaded the machine and added Services Status…
F-*-C-K!!! It added 4 items on the dashboard!!! WTF, I am still on 2.03!!!
NOW I AM PISSED! This (I feel) could have been resolved in 2.1 without impacting my users or my system...
*(@$#%&
and you can see my frustration!!!
cyber7-out -
http://forum.pfsense.org/index.php?topic=52441.0
nuff said :( -
F-*-C-K!!! It added 4 items on the dashboard!!! WTF, I am still on 2.03!!!
NOW I AM PISSED! This (I feel) could have been resolved in 2.1 without impacting my users or my system…So, you reverted to a snapshot before 2.1 upgrade, and are pissed that you are back to 2.0.x? Errr? Sound like it's exactly what's it supposed to be like, no?! Also, I cannot see how you fixing the WS issue by this, since - as you've yourself noted - there's no uninstaller for the thing apparently.
Meanwhile, since you are running this on a VM:
- create a new VM
- do a clean 2.1 install (which will not be screwed by any widescreen and other patches)
- first fix the broken duplicate section in config.xml you identified before
- restore the config backup
- let it reboot and reinstall the packages
- switch over to this new VM
- all done, profit
-
Ok, now that I am a bit calmer.
NOTE:
There is an UNINSTALL for WideScreen in 2.03. There is an Installer for Widescreen in 2.03…What happened:
After I returning to the 2.03 snapshot I:
1. Uninstalled the Widescreen and other packages (as specified previously.
2. Rebooted the machine...
Problem (duplicate Dashboard entries) still there...
1. I then made a backup and removed the entries from the BACKUP config.xml file (as specified before)
2. I then imported the XML file, rebooted...
Problem (duplicate Dashboard entries) still there...AND: They increase with every SAVE!
So, I am not a novice, just HIGHLY irritated by poor code...
I am now in the process of recreating the entire environment (leaving the old pfSense in place) and once completed, I will swop the two VM's.
cyber7-out
-
Thats too bad.
I had hoped that if you had removed the package, backed up settings, installed from scratch a new pfsense 2.1 then restored your settings you might have saved yourself some work. I'm sorry to hear that didn't work out.
Not sure if you actually ever tried it that way, but yeah. Its a pain for sure.
-
Oh well, I suppose sometimes I also have to re-create VM's from scratch. I just hate the tedious work of re-doing forms…
Actually, as hindsight, I am glad it happened. This will force me to remove 5 years of rubbish in the environment.
cyber7-out
-
It's not problem but I'm having the same bug with server status widget on some servers (2.0.2 and 2.1) . I get multiple similar widget windows and I don't use widescreen.
