The Official *nix Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
The disk is in a removable drive and moves between one of 70 machines that's identical in hardware.. apart from the MAC address of the card. Hence adding the MAC in will only be correct for that machine.. until it moves again.
As mentioned, this didn't seem to be an issue in FC4,5, etc... just 7 that I've noticed it happenning.
Kudzu doesn't kick in (not visually, I mean) but one of the network-functions procedures (functions) seems to have been modified in some way - the comments mention a deprecated argument and I know for a fact that function is getting called. I just don't know how to frig it so that it reads the existing MAC and slip it into the ifcfg-eth0 file before the network start (ie: before "/etc/init.d/network start" kicks in).
As mentioned, this didn't seem to be an issue in FC4,5, etc... just 7 that I've noticed it happenning.
Kudzu doesn't kick in (not visually, I mean) but one of the network-functions procedures (functions) seems to have been modified in some way - the comments mention a deprecated argument and I know for a fact that function is getting called. I just don't know how to frig it so that it reads the existing MAC and slip it into the ifcfg-eth0 file before the network start (ie: before "/etc/init.d/network start" kicks in).
-
seanyseansean
- Baa!

- Posts: 97
- Joined: Wed Jan 23, 2008 11:17 am 0
Re: The Official *nix Thread
(from memory) there are two arguments you can use HWADDR (the real MAC) or MACADDR, which is a made-up MAC that you can assign to the device. Have you tried the latter to see if it helps?Dungeon-Dave wrote:The disk is in a removable drive and moves between one of 70 machines that's identical in hardware.. apart from the MAC address of the card. Hence adding the MAC in will only be correct for that machine.. until it moves again.
As mentioned, this didn't seem to be an issue in FC4,5, etc... just 7 that I've noticed it happenning.
Kudzu doesn't kick in (not visually, I mean) but one of the network-functions procedures (functions) seems to have been modified in some way - the comments mention a deprecated argument and I know for a fact that function is getting called. I just don't know how to frig it so that it reads the existing MAC and slip it into the ifcfg-eth0 file before the network start (ie: before "/etc/init.d/network start" kicks in).
-
seanyseansean
- Baa!

- Posts: 97
- Joined: Wed Jan 23, 2008 11:17 am 0
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
mmm.. fuck... DEAD useful page. Yah, If I pick a MAC for it, it should (hopefully) override the onboard NIC and (hopefully) not change other networking info.
Ta for that! I'll give it a go when I'm back at work.
Ta for that! I'll give it a go when I'm back at work.
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Gnngh.
Anyone used pop-before-smtp.pl with PostFix before? Postfix doesn't want to read the db file. My /var/log/maillog sez: -
My first thought was that the Perl DB_File was using a different DB format, yet thats not what I found...
I figured even though PostFix isn't using the aliases.db file (on account of using virtual hosting via MySQL), the file format would still be something that its happy with.
The upshot of this means that anyone whose IP is not in PostFix's mynetworks directive will have to use the webmail interface I've set up rather than Outlook because no doubt they'll be on home broadband connections with DHCP assigned IPs which cannot be added to PostFix list of trusted IPs.
I just wish I knew why the bloody thing refuses to read the db file. Tried everything here: - http://popbsmtp.sourceforge.net/debug.shtml to no avail.
Anyone used pop-before-smtp.pl with PostFix before? Postfix doesn't want to read the db file. My /var/log/maillog sez: -
Code: Select all
fatal: error reading /etc/postfix/pop-before-smtp.db: Unknown error 4294936319
Code: Select all
[root@localhost postfix]# file aliases.db
aliases.db: Berkeley DB (Hash, version 8, native byte-order)
[root@localhost postfix]# file pop-before-smtp.db
pop-before-smtp.db: Berkeley DB (Hash, version 8, native byte-order)
The upshot of this means that anyone whose IP is not in PostFix's mynetworks directive will have to use the webmail interface I've set up rather than Outlook because no doubt they'll be on home broadband connections with DHCP assigned IPs which cannot be added to PostFix list of trusted IPs.
I just wish I knew why the bloody thing refuses to read the db file. Tried everything here: - http://popbsmtp.sourceforge.net/debug.shtml to no avail.
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Nevermind - fixed. File command was either lying or only reading the file header to find out what the format was. A quick uncomment of some stuff in the PostFix config seems to have fixed it.
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
This is a strange one....we've just installed phpBB3 on our website for our forum under httpd (Apache) and under /etc/httpd/conf.d/php.conf theres the usual: -
and in the regular httpd.conf theres the line which includes the php.conf: -
but when browsing to http://<my server>/phpBB3/ it just displays the directory listing as though its not picking up the DirectoryIndex entry. I even tried changing the path from relative to absolute, so: -
...becomes:-
and I've definitely restarted Apache in the meantime to no avail. Its definitely picking up the php.conf file as the forum works fine if you hit the index.php page manually.
Code: Select all
DirectoryIndex index.php
Code: Select all
Include conf.d/*.conf
Code: Select all
Include conf.d/*.conf
Code: Select all
Include /etc/httpd/conf.d/*.conf
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Wibble
- Baaaaaa!

- Posts: 3317
- Joined: Fri May 02, 2003 10:13 pm 0
- XBL Gamertag: misterwibble
- Location: The Hague - The Netherlands
- Contact:
Re: The Official *nix Thread
Maybe AllowOverride sits in the way? Not sure why, but hey.
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
1. Add another fake index page next to index.php, eg: "start.html" with some regocnisible gumpf in it.
2. Browse to http://<my server>/phpBB3/start.html and see if it comes up.
- if it doesn't, then you've got misconfigured virtual hosting
- if it does, then there's possibly a .htaccess or some other later config that's overriding the DirectoryIndex directive.
3. tail -f /var/log/httpd/access.log - see what site, file etc was accessed. Also check the error log, see if there's some other config setting that's kicking it to a different page (fucking welcome.html redirect, anyone?)
nb: RageM, I teach Apache courses and know a lot about common faults with misconfigured Apache servers - I won't say I know ALL there is to know about Apache, but IME most "Apache beginners" manage to get (what they deem) success after about 25% of the effort required, and mistakenly feel that's all they need to do... leaving a vulnerable and misconfigured server ripe for the picking. Don't confuse results with success. If you want some suggestions and a hand on this front, feel free to PM me.
Just as a matter of interest... you ARE editing the correct files, aren't you? I spent ages pissing around with files in /etc/httpd on one boxen before learning someone had downloaded & compiled apache manually into /usr/local/apache. They're only still alive because it's illegal to kill them.
2. Browse to http://<my server>/phpBB3/start.html and see if it comes up.
- if it doesn't, then you've got misconfigured virtual hosting
- if it does, then there's possibly a .htaccess or some other later config that's overriding the DirectoryIndex directive.
3. tail -f /var/log/httpd/access.log - see what site, file etc was accessed. Also check the error log, see if there's some other config setting that's kicking it to a different page (fucking welcome.html redirect, anyone?)
nb: RageM, I teach Apache courses and know a lot about common faults with misconfigured Apache servers - I won't say I know ALL there is to know about Apache, but IME most "Apache beginners" manage to get (what they deem) success after about 25% of the effort required, and mistakenly feel that's all they need to do... leaving a vulnerable and misconfigured server ripe for the picking. Don't confuse results with success. If you want some suggestions and a hand on this front, feel free to PM me.
Quick tip: try "/etc/init.d/httpd reload" to refresh apache's settings, bit quicker than a reload. Also "/etc/init.d/httpd configtest" before restarting/reloading to run a sanity-check against apache's config files.RageMatrix wrote:and I've definitely restarted Apache in the meantime to no avail.
Just as a matter of interest... you ARE editing the correct files, aren't you? I spent ages pissing around with files in /etc/httpd on one boxen before learning someone had downloaded & compiled apache manually into /usr/local/apache. They're only still alive because it's illegal to kill them.
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Funny you should mention that.....Dungeon-Dave wrote: Just as a matter of interest... you ARE editing the correct files, aren't you? I spent ages pissing around with files in /etc/httpd on one boxen before learning someone had downloaded & compiled apache manually into /usr/local/apache. They're only still alive because it's illegal to kill them.
I noticed that the port on the conf file I was edited was pointing at port 9090 instead of 80. "Thats odd," I thought, "because the server is definitely listening on port 80". Quick fumble to /usr/local/apache.
"Well, son of a bitch....!"
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
What distro is this running on, BTW?
You may benefit from the distro-specific installation of Apache, rather than the localised install - ie: ditch the one in /usr/local.
You may benefit from the distro-specific installation of Apache, rather than the localised install - ie: ditch the one in /usr/local.
- JQW
- Baaaaa!

- Posts: 1186
- Joined: Thu Feb 22, 2007 12:23 pm 0
- Location: Ripon, where nothing ever happens.
Re: The Official *nix Thread
I had the same once with three(!) separate local installations of Samba, as well as the standard version installed in the usual place, with all four configured differently. The machine had been powered down to be relocated, and wasn't configured to restart Samba automatically once in its new location. Samba was only needed for one particular development project, and so it was just forgotten about until the project was restarted about a year later.Dungeon-Dave wrote: Just as a matter of interest... you ARE editing the correct files, aren't you? I spent ages pissing around with files in /etc/httpd on one boxen before learning someone had downloaded & compiled apache manually into /usr/local/apache. They're only still alive because it's illegal to kill them.
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Can't, I'm afraid. Its being used for running a Nagios server. There seem to be three web servers running on that machine - Resin, and two copies of Apache. I gather theres a good reason for it, although I've not been told exactly what those reasons areDungeon-Dave wrote:What distro is this running on, BTW?
You may benefit from the distro-specific installation of Apache, rather than the localised install - ie: ditch the one in /usr/local.
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
- Dungeon-Dave
- Baaaaaa!

- Posts: 3925
- Joined: Thu Aug 04, 2005 12:01 pm 0
- Location: UK
- Contact:
Re: The Official *nix Thread
THREE webservers?
I sincerely hope that whoever decided to do that:
(a) isn't trying to run live AND production on the same box
(b) knows how to do virtual hosting in Apache (and thus has very good reasons not to go down that route)
Dude, I urge you to find out *why* it's configured in that fashion. I'm not saying that there could be valid reasons, but I'd HATE the reason to be "we weren't skilled enough to know how to do it properly at the time and now we're comfortable with using a misconfigured server"... and you're stuck with trying to work on it.
FWIW... all servers I maintain (or help maintain ... mmmm... probably about 5, maybe up to
serve multiple sites, multiple domains, multiple directories on multiple ports... but all have one instance of Apache running.
I sincerely hope that whoever decided to do that:
(a) isn't trying to run live AND production on the same box
(b) knows how to do virtual hosting in Apache (and thus has very good reasons not to go down that route)
Dude, I urge you to find out *why* it's configured in that fashion. I'm not saying that there could be valid reasons, but I'd HATE the reason to be "we weren't skilled enough to know how to do it properly at the time and now we're comfortable with using a misconfigured server"... and you're stuck with trying to work on it.
FWIW... all servers I maintain (or help maintain ... mmmm... probably about 5, maybe up to
- RageMatrix
- Baaaaaaa!

- Posts: 5515
- Joined: Fri May 10, 2002 12:52 pm 0
- XBL Gamertag: Jon256
- Location: East Sussex
Re: The Official *nix Thread
Uh-huh. Theres Nagios running on one instance and Resin and the other Apache are linked via Virtual hosting to serve up our test site. I gather its because the router firewall is open for one of the Apaches, but not for the Nagios server, which is internal only.Dungeon-Dave wrote:THREE webservers?
I sincerely hope that whoever decided to do that:
(a) isn't trying to run live AND production on the same box
(b) knows how to do virtual hosting in Apache (and thus has very good reasons not to go down that route)
Dude, I urge you to find out *why* it's configured in that fashion. I'm not saying that there could be valid reasons, but I'd HATE the reason to be "we weren't skilled enough to know how to do it properly at the time and now we're comfortable with using a misconfigured server"... and you're stuck with trying to work on it.
FWIW... all servers I maintain (or help maintain ... mmmm... probably about 5, maybe up toserve multiple sites, multiple domains, multiple directories on multiple ports... but all have one instance of Apache running.
XBox Gamertag: Jon256
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread
Wii Code: 4849 1090 9042 6725
"Wrapped in metal, wrapped in ivy"
The Official UNIX/Linux Thread