| View previous topic :: View next topic |
| Author |
Message |
ShiroiKuma
n00b
Joined: 09 Nov 2012
Posts: 40
Location: Japan
|
 Posted: Tue Sep 02, 2014 9:15 am Post subject: [SOLVED] distcc ignoring config file |
 |
|
I've got distcc emerged on my nice i5 and on my crummy old laptop. The laptop is trying to distribute to my i5 pc however it's being refused apparently.
On the i5 I've allowed the IP of my laptop as per
/etc/conf.d/distccd
| Code: | DISTCCD_OPTS="--port 3632 --log-level debug --log-file /var/log/distccd.log -N 15"
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.11.6" |
Everything else is left as default. However the output of
systemctl status distccd indicates it's being ignored
| Code: | > # systemctl status distccd
● distccd.service - Distccd: A Distributed Compilation Server
Loaded: loaded (/usr/lib64/systemd/system/distccd.service; disabled)
Drop-In: /etc/systemd/system/distccd.service.d
└─00gentoo.conf
Active: active (running) since Tue 2014-09-02 18:06:16 JST; 6min ago
Main PID: 18990 (distccd)
CGroup: /system.slice/distccd.service
├─18990 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
├─18992 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
├─19022 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
├─19023 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
├─19055 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
├─19056 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
└─19057 /usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow 127.0.0.1
Sep 02 18:09:41 hoganji distccd[19055]: (dcc_check_client) ERROR: connection from client '192.168.11.6:35855' denied by access list
Sep 02 18:10:41 hoganji distccd[19056]: (dcc_check_client) connection from 192.168.11.6:35857
Sep 02 18:10:41 hoganji distccd[19056]: (dcc_check_address) deny client 0x60ba8c0, value 0x100007f, mask 0xffffffff
Sep 02 18:10:41 hoganji distccd[19056]: (dcc_check_client) ERROR: connection from client '192.168.11.6:35857' denied by access list
Sep 02 18:11:41 hoganji distccd[19057]: (dcc_check_client) connection from 192.168.11.6:35859
Sep 02 18:11:41 hoganji distccd[19057]: (dcc_check_address) deny client 0x60ba8c0, value 0x100007f, mask 0xffffffff
Sep 02 18:11:41 hoganji distccd[19057]: (dcc_check_client) ERROR: connection from client '192.168.11.6:35859' denied by access list
Sep 02 18:12:43 hoganji distccd[18992]: (dcc_check_client) connection from 192.168.11.6:35861
Sep 02 18:12:43 hoganji distccd[18992]: (dcc_check_address) deny client 0x60ba8c0, value 0x100007f, mask 0xffffffff
Sep 02 18:12:43 hoganji distccd[18992]: (dcc_check_client) ERROR: connection from client '192.168.11.6:35861' denied by access list
|
The command is running but only allowing 127.0.0.1 and it's not even logging as per the configuration file. I'm still googling around to find a cause of this but not having much luck.
Can anyone see what's wrong here? At first I was allowing 192.168.11.0/24 to allow my whole network, but then figured... maybe I've got it wrong... I'll just add the IP directly while testing.
Last edited by ShiroiKuma on Wed Sep 03, 2014 7:46 am; edited 1 time in total |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA
|
| Posted: Tue Sep 02, 2014 10:54 pm Post subject: |
|
|
Did you restart distcc? systemctl restart distccd ? or something like that? (or stop and then start it?) (sorry I don't have any servers using systemd yet to get the right syntax...)
After you stop it, do the processes still show up?
The process list still looks like it's only allowing 127.0.0.1 which corresponds with the errors seen in the log.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
ShiroiKuma
n00b
Joined: 09 Nov 2012
Posts: 40
Location: Japan
|
| Posted: Wed Sep 03, 2014 7:46 am Post subject: |
|
|
Finally I found out how to set the --allow parameters "correctly".
The service file is as follows:
| Code: | [Unit]
Description=Distccd: A Distributed Compilation Server
After=network.target
[Service]
User=distcc
ExecStart=/usr/bin/distccd --verbose --no-detach --daemon --port 3632 -N 15 --allow $ALLOWED_SERVERS
[Install]
WantedBy=multi-user.target
|
I altered this line here to force my network instead of ALLOWED_SERVERS, but I've just found that the file
/etc/systemd/system/distccd.service.d/00gentoo.conf
Let's you set ALLOWED_SERVERS and now my systemctl status distccd shows the correct allow settings and it's working fine now.
It'd be nice if I didn't need to alter the service file to change where the log file goes (for now journalctl is okay). |
|
| Back to top |
|
|
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA
|
| Posted: Wed Sep 03, 2014 3:36 pm Post subject: |
|
|
Ugh... That's annoying. Wish they used the same config file but it figures that two different files are used for systemd and openrc. I guess this is a proof point that they will diverge, and having systemd installed while still running openrc can cause weird behavior...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
|
Portage & Programming
