alfred: IPC issues

B.A.T.M.A.N. Jan Lühr 3 participants 5 messages Aug 6, 2014 – Aug 7, 2014

lore

Share & tools

lore

Jan Lühr

author

2014-08-06 18:32 UTC #0 lore raw

Hei folks,

I'm using alfred 2014.0.0 on OpenWRT Barrier Breaker.

Alfred is running:

root@6466b34ffcac:~# ps -w | grep alfred
 1718 root      1100 S    /usr/sbin/alfred -i br-freifunk -b bat0

But cannot be queried using the client:

root@6466b34ffcac:~# alfred -r 94
can't connect to unix socket: Connection refused

What's wrong here?

Configuration is
config 'alfred' 'alfred'
option interface 'br-freifunk'
option mode 'server'
option batmanif 'bat0'
option start_vis '0'
option run_facters '0'

Thanks,
Keep smiling
yanosz

Simon Wunderlich

2014-08-07 08:37 UTC #1 lore raw

Hello Jan,

Quoted 14 lines

Hei folks,
I'm using alfred 2014.0.0 on OpenWRT Barrier Breaker.
Alfred is running:
root@6466b34ffcac:~# ps -w | grep alfred
 1718 root      1100 S    /usr/sbin/alfred -i br-freifunk -b bat0
But cannot be queried using the client:
root@6466b34ffcac:~# alfred -r 94
can't connect to unix socket: Connection refused
What's wrong here?

Quoted 8 lines

Configuration is
config 'alfred' 'alfred'
option interface 'br-freifunk'
option mode 'server'
option batmanif 'bat0'
option start_vis '0'
option run_facters '0'

I don't see a problem right from your configuration. Can you please check:

* do you see the socket file /var/run/alfred.sock after starting alfred?
* does the same problem happen if you restart alfred or start it manually?

Thank you,
Simon

Jan Lühr

author

2014-08-07 08:42 UTC #2 lore raw

Hello,

thanks for your feedback.

Am 08/07/2014 10:37 AM, schrieb Simon Wunderlich:

Quoted 16 lines

Hello Jan,
Quoted 14 lines
Hei folks,
I'm using alfred 2014.0.0 on OpenWRT Barrier Breaker.
Alfred is running:
root@6466b34ffcac:~# ps -w | grep alfred
 1718 root      1100 S    /usr/sbin/alfred -i br-freifunk -b bat0
But cannot be queried using the client:
root@6466b34ffcac:~# alfred -r 94
can't connect to unix socket: Connection refused
What's wrong here?

(...)

Quoted 3 lines

I don't see a problem right from your configuration. Can you please check:
* do you see the socket file /var/run/alfred.sock after starting alfred?

Looks nice..

root@6466b34ffcac:~# ls -lh /var/run/alfred.sock
srwxr-xr-x    1 root     root           0 Aug  6 20:47 /var/run/alfred.sock

Quoted 1 line

* does the same problem happen if you restart alfred or start it manually?

/etc/init.d/alfred restart made it disappear

For some reason, this is persistent:
* Before restarting, alfred was unusable after rebooting the machine
* After a restarting once, alfred is usable - even after reboots

Greetu, Jan

Jan Lühr

author

2014-08-07 12:34 UTC #3 lore raw

In reply to Simon Wunderlich

Hello,

Am 08/07/2014 10:37 AM, schrieb Simon Wunderlich:

Quoted 6 lines

Hello Jan,
Quoted 4 lines
Hei folks,
I'm using alfred 2014.0.0 on OpenWRT Barrier Breaker.

I'm not able to reproduce this issue using 2014.3.0. I'm not certain, whether 2014.3.0 is the cause.

Greetz, Jan

Matthias Schiffer

2014-08-07 13:18 UTC #4 lore raw

Quoted 8 lines · Jan Lühr

Hello,
Am 08/07/2014 10:37 AM, schrieb Simon Wunderlich:
Quoted 4 lines
Hello Jan,
Quoted 2 lines
Hei folks,

Quoted 8 lines

Quoted 2 lines
Quoted 2 lines
I'm using alfred 2014.0.0 on OpenWRT Barrier Breaker.
I'm not able to reproduce this issue using 2014.3.0. I'm not certain, whether 2014.3.0 is the cause.
Greetz, Jan

I think 2014.0.0 had an FD leak issue, which could easily cause alfred to exceed the process limit (which is 1024 FDs on OpenWrt) within a few hours. As accept() needs to open a new FD, this would explain the issue.

Matthias