[BlueOnyx:11496] Re: Network interface problem

2012-10-04 Thread Jeff Folk
On Oct 4, 2012, at 10:03 PM, Michael Stauber wrote: > Hi Jeff, > >> Removed the old udev device mapping file >> Modified grub.conf to have biosdevname=0 at the end of the kernel line >> Rebooted >> >> Both interfaces came up (although reverse of before - pci card is now LAN, >> and built-in is

[BlueOnyx:11495] Re: Network interface problem

2012-10-04 Thread Gerald Waugh
On 10/04/2012 10:03 PM, Michael Stauber wrote: Hi Jeff, Removed the old udev device mapping file Modified grub.conf to have biosdevname=0 at the end of the kernel line Rebooted Both interfaces came up (although reverse of*before - pci card is now LAN, and built-in is WAN*), however, I am stil

[BlueOnyx:11494] Re: Fan / Disk status broke

2012-10-04 Thread Michael Stauber
Hi George, > The Active Monitor Overview shows gray ball-dots for fans and disk > integrity. It does show Fan status? O.o Actually the GUI is not supposed to do that. And if it would show it, there would be no data, as Active Monitor doesn't monitor these anymore. That was kinda removed after th

[BlueOnyx:11493] Re: Network interface problem

2012-10-04 Thread Michael Stauber
Hi Jeff, > Removed the old udev device mapping file > Modified grub.conf to have biosdevname=0 at the end of the kernel line > Rebooted > > Both interfaces came up (although reverse of before - pci card is now LAN, > and built-in is WAN), however, I am still getting swatch errors: > > Very inte

[BlueOnyx:11492] Re: OpenWebmail gdbm fatal: read error

2012-10-04 Thread Chris Gebhardt - VIRTBIZ Internet
Hi Richard, Richard Morgan wrote: > There are a few extensions in the .openwebmail/db directory: .cache, db, > dir, pag. Renaming one of these then doing the rebuild seemed to do the > trick. Sorry, I don't know which one - I'd guess either .dir or .pag, but > it is only a guess. Thanks, I ap

[BlueOnyx:11491] Re: Network interface problem

2012-10-04 Thread Jeff Folk
On Oct 4, 2012, at 3:52 PM, Chris Gebhardt - VIRTBIZ Internet wrote: > Jeff Folk wrote: >> Had a hardware failure last night… My trusty, dusty Dimension 5150 finally >> croaked. So, to get my hobby server up again, I swapped the drives into a >> spare Optiplex GX 620. Booted with no problems, or

[BlueOnyx:11490] Re: OpenWebmail gdbm fatal: read error

2012-10-04 Thread Richard Morgan
- Original Message - From: "Chris Gebhardt - VIRTBIZ Internet" To: "BlueOnyx General Mailing List" Sent: Thursday, October 04, 2012 9:59 PM Subject: [BlueOnyx:11488] OpenWebmail gdbm fatal: read error > This is a BX 5108R box running Solarspeed's OpenWebmail. > > Customer reported a pr

[BlueOnyx:11489] Re: Network interface problem

2012-10-04 Thread Jeff Folk
On Oct 4, 2012, at 3:52 PM, Chris Gebhardt - VIRTBIZ Internet wrote: > Jeff Folk wrote: >> Had a hardware failure last night… My trusty, dusty Dimension 5150 finally >> croaked. So, to get my hobby server up again, I swapped the drives into a >> spare Optiplex GX 620. Booted with no problems, o

[BlueOnyx:11488] OpenWebmail gdbm fatal: read error

2012-10-04 Thread Chris Gebhardt - VIRTBIZ Internet
This is a BX 5108R box running Solarspeed's OpenWebmail. Customer reported a problem this afternoon accessing OpenWebmail. It's the old "Internal Server Error" business. I've ensured that the user is not over quota. Checking /var/log/httpd/error_log I see this from when I try and access the

[BlueOnyx:11487] Re: Network interface problem

2012-10-04 Thread Chris Gebhardt - VIRTBIZ Internet
Jeff Folk wrote: > Had a hardware failure last night… My trusty, dusty Dimension 5150 finally > croaked. So, to get my hobby server up again, I swapped the drives into a > spare Optiplex GX 620. Booted with no problems, or so I thought… > > I get an admin mail stating that eth1 is down (eth1 is

[BlueOnyx:11486] Network interface problem

2012-10-04 Thread Jeff Folk
Had a hardware failure last night… My trusty, dusty Dimension 5150 finally croaked. So, to get my hobby server up again, I swapped the drives into a spare Optiplex GX 620. Booted with no problems, or so I thought… I get an admin mail stating that eth1 is down (eth1 is my on-board nic, set to lo