| View previous topic :: View next topic |
| Author |
Message |
yagaev
n00b
Joined: 10 Jan 2017
Posts: 27
|
 Posted: Thu Feb 16, 2017 3:22 pm Post subject: cannot start distccd |
 |
|
Cannot start distccd. Pls help
| Code: | service distccd start
* Bringing up interface sit0
* ERROR: interface sit0 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.sit0 failed to start
* ERROR: cannot start distccd as net.sit0 would not start
ni@localhost:~$ sudo leafpad /etc/conf.d/distccd
/usr/share/themes/MurrinaFancyCandy/gtk-2.0/gtkrc:46: Murrine configuration option "scrollbar_color" is no longer supported and will be ignored.
|
ipv6 is disabled
| Code: | cat /etc/sysctl.conf |grep ipv6
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.wlp7s0.autoconf=0
net.ipv6.conf.wlp7s0.accept_ra=0
|
| Code: | ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1 (Local Loopback)
RX packets 4032 bytes 869984 (849.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4032 bytes 869984 (849.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.39 netmask 255.255.255.0 broadcast 192.168.1.255
ether 94:39:e5:bc:33:bb txqueuelen 1000 (Ethernet)
RX packets 133641 bytes 136760641 (130.4 MiB)
RX errors 0 dropped 986 overruns 0 frame 0
TX packets 96549 bytes 18633952 (17.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 |
|
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W
|
| Posted: Thu Feb 16, 2017 3:35 pm Post subject: |
|
|
yagaev,
sit0 is an IP6 over Ip4 tunnel endpoint that comes with IPv6 support in the kernel.
In /etc/rc.conf you will have
| Code: | # Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES" |
Set that to | Code: | | rc_depend_strict="NO" |
so that any interface will provide the net service.
Your ifconfig shows only a wifi interface. Even if its ac and you get the full 1.2G bit/sec, its still only half duplex, which will slow distcc considerably.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
yagaev
n00b
Joined: 10 Jan 2017
Posts: 27
|
| Posted: Sat Feb 18, 2017 2:31 pm Post subject: |
|
|
| thank you! already compiling |
|
| Back to top |
|
|
jlpoole
Guru
Joined: 01 Nov 2005
Posts: 483
Location: Salem, OR
|
| Posted: Tue Sep 12, 2023 2:32 am Post subject: |
|
|
| NeddySeagoon wrote: | yagaev,
sit0 is an IP6 over Ip4 tunnel endpoint that comes with IPv6 support in the kernel.
In /etc/rc.conf you will have
| Code: | # Do we allow any started service in the runlevel to satisfy the dependency
# or do we want all of them regardless of state? For example, if net.eth0
# and net.eth1 are in the default runlevel then with rc_depend_strict="NO"
# both will be started, but services that depend on 'net' will work if either
# one comes up. With rc_depend_strict="YES" we would require them both to
# come up.
#rc_depend_strict="YES" |
Set that to | Code: | | rc_depend_strict="NO" |
so that any interface will provide the net service.
Your ifconfig shows only a wifi interface. Even if its ac and you get the full 1.2G bit/sec, its still only half duplex, which will slow distcc considerably. |
Neddy's suggested modification solved a problem that I had been laboring over for an hour+. I was having problems on a Xen VM getting distcc to run. I kept getting:
| Code: | rpicc /etc # /etc/init.d/distccd start
* Bringing up interface eth0
* ERROR: interface eth0 does not exist
* Ensure that you have loaded the correct kernel module for your hardware
* ERROR: net.eth0 failed to start
* ERROR: cannot start distccd as net.eth0 would not start
rpicc /etc # date
Mon Sep 11 18:59:34 PDT 2023
rpicc /etc #
|
Xen renamed my network interface to enX0. So after reading Neddy's suggestion above, I modified /etc/rc.conf as follows (using "nano -l", so the line numbers are an artifact of my editing session and should not be in the saved file):
| Code: | 30 #rc_depend_strict="YES"
31 #
32 # 9/12/2023 jlpoole: trying to fix problem with distcc daemon not starting
33 # because it cannot find eth0
34 # per: https://forums.gentoo.org/viewtopic-t-1059478-start-0.html
35 #
36 rc_depend_strict="NO"
37 |
I then simply ran
and the distcc daemon started. No need for reboot or start/stop of anything. Thank you, Neddy! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54237
Location: 56N 3W
|
| Posted: Tue Sep 12, 2023 11:46 am Post subject: |
|
|
jlpoole,
If you don't have an eth0, you should not have a /etc/init.d/net.eth0 file either.
The it won't be started and fail.
| Code: | | rc_depend_strict="NO" |
is inteded for situations where you have two or more interfaces, like a laptop with wifi and wired, and you don't care which one comes up.
You should have a /etc/init.d/net.enX0 which is a symlink to net.lo. Then you add net.enX0 to the default runlevel.
In other words, it works as is but for the wrong reason.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
jlpoole
Guru
Joined: 01 Nov 2005
Posts: 483
Location: Salem, OR
|
| Posted: Tue Sep 12, 2023 3:42 pm Post subject: Fixed -- the right way |
|
|
| NeddySeagoon wrote: | jlpoole,
If you don't have an eth0, you should not have a /etc/init.d/net.eth0 file either.
The it won't be started and fail.
| Code: | | rc_depend_strict="NO" |
is inteded for situations where you have two or more interfaces, like a laptop with wifi and wired, and you don't care which one comes up.
You should have a /etc/init.d/net.enX0 which is a symlink to net.lo. Then you add net.enX0 to the default runlevel.
In other words, it works as is but for the wrong reason. |
Yes! Thank you, NeddySeagoon for this valuable insight. You are correct [again].
I stopped /etc/init.d/distccd, rem'd out my edit in /etc/rc.conf.
I did have a softlink /etc/init.d/net.eth0 -> /etc/init.d/net.lo along with a softlink net.enX0 -> /etc/init.d/net.lo.
I removed the /etc/init.d/net.eth0 and successfully started distccd. I rebooted (just to make sure the removal of eth0 did not cause problems) and I successfully logged into the VM and found /etc/init.d/distccd started as it should have.
Problem solved the correct way. Thank you, again, for reading my previous post and taking the time to explain and correct the condition. Hopefully others reading this will take note. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
