Hello,

thanks for your feedback.

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

Hello Jan,

...

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?

(...)

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

• 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

On 08/07/2014 02:34 PM, Jan Lühr wrote:

Hello,

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

...

Hello Jan,

...

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

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