| View previous topic :: View next topic |
| Author |
Message |
ocZer
n00b
Joined: 28 Jun 2005
Posts: 36
Location: Drammen, Norway
|
 Posted: Mon Feb 21, 2011 2:00 pm Post subject: |
 |
|
I dont think it's a bug really, but im no expert. I think it's just warning that a service has been started twice.
Could u maybe give us the output of your init log and | Code: | | rc-update show default |
_________________
kernel 2.6.36-gentoo-r5 x86_64 - Acer 4820tg laptop |
|
| Back to top |
|
 |
Warhead
Tux's lil' helper
Joined: 09 Oct 2003
Posts: 122
Location: Verden, near Bremen, Germany
|
| Posted: Mon Feb 21, 2011 6:01 pm Post subject: |
|
|
| ocZer wrote: | | rc-update show default |
Here it is:
| Code: |
# rc-update show default
apache2 | default
dhcpd | default
iptables | default
local | default
mysql | default
named | default
net.eth1 | default
netmount | default
pppoe | default
sshd | default
syslog-ng | default
udev-postmount | default
vixie-cron | default
#
|
Regards
Warhead
_________________
To Rome said Nero: "If to smoke you turn
I shall not cease to fiddle while you burn."
To Nero Rome replied: "Pray do your worst,
'Tis my excuse that you were fiddling first."
--Orm Pludge |
|
| Back to top |
|
|
ocZer
n00b
Joined: 28 Jun 2005
Posts: 36
Location: Drammen, Norway
|
| Posted: Wed Feb 23, 2011 2:01 pm Post subject: |
|
|
It appears that the reason for the message is the same on yours as it was on mine, but as you mention that u cannot remove dhcpd because it works as a routing device im not certain how to go around it.
I understand that you have a second network card then, but i cannot see it listed. It's probably called up by udev. On my setup all network cars are called by udev and i didnt have to add them with rc-update. dhcpd is called by the network card itself on boot. If you can make your eth1 device also work this way you could remove them from rc-update.
_________________
kernel 2.6.36-gentoo-r5 x86_64 - Acer 4820tg laptop |
|
| Back to top |
|
|
Warhead
Tux's lil' helper
Joined: 09 Oct 2003
Posts: 122
Location: Verden, near Bremen, Germany
|
| Posted: Wed Feb 23, 2011 3:57 pm Post subject: |
|
|
| ocZer wrote: | It appears that the reason for the message is the same on yours as it was on mine, but as you mention that u cannot remove dhcpd because it works as a routing device im not certain how to go around it.
I understand that you have a second network card then, but i cannot see it listed. It's probably called up by udev. On my setup all network cars are called by udev and i didnt have to add them with rc-update. dhcpd is called by the network card itself on boot. If you can make your eth1 device also work this way you could remove them from rc-update. |
You are right. I will try to get the device up via udef. Can this have an effect on pppoe on the device? Or is there no difference to pppoe how the device was brought up?
Regards
Warhead
_________________
To Rome said Nero: "If to smoke you turn
I shall not cease to fiddle while you burn."
To Nero Rome replied: "Pray do your worst,
'Tis my excuse that you were fiddling first."
--Orm Pludge |
|
| Back to top |
|
|
ocZer
n00b
Joined: 28 Jun 2005
Posts: 36
Location: Drammen, Norway
|
| Posted: Wed Feb 23, 2011 4:52 pm Post subject: |
|
|
Im not certain how this would affect pppoe. I have never used this directly from pc, but always had a router to do the job.
_________________
kernel 2.6.36-gentoo-r5 x86_64 - Acer 4820tg laptop |
|
| Back to top |
|
|
klhsieh
n00b
Joined: 10 Aug 2010
Posts: 5
|
| Posted: Sat Mar 12, 2011 6:33 am Post subject: |
|
|
| jwdonal wrote: | | My fix was to simply reboot the machine. I was receiving exactly the same error as all of you but I found another forum that stated that this error can occur if the network interface does not start up on boot. If you start the device after boot (i.e. after you login, using /etc/init.d/eth0 start) this error can occur. It happens because the 'net' process is already started or something like that. I really don't know specifically what scenario or combination of settings causes the problem but I just thought I would post my solution and findings here in case it helps someone else. |
Jwdonal's solution works for me!
Originally, my syslog-ng has wrong configuration. After I fixed the conf file, I get "Cannot add provide 'net', as a service with the same name exists!" error.
I have tried above methods but they did not work.
After rebooting, those problem have gone and my apache can work! |
|
| Back to top |
|
|
|
Networking & Security
