zmf .sock error

Support and queries relating to all previous versions of ZoneMinder
Locked
bjoern
Posts: 2
Joined: Thu Jun 17, 2004 5:36 pm
Location: germany

zmf .sock error

Post by bjoern »

hi!

my problem is only a minor one.. i have 2 cams up + running with ZM ( VERY good tool btw!! ). one local cam ( /dev/video0 @monitor 2 ) and one netcam ( @monitor 7 ), running over a http server in my LAN. no problems so far, just the frame daemon for the local cam cant' bind a socket.

from my /var/messages:
Jun 18 13:28:43 linux zmf-m2[3653]: INF [Debug Level = 0, Debug Log = ]
Jun 18 13:28:43 linux zmf-m2[3653]: WAR [Can't unlink '/tmp/zmf-2.sock': Operation not permitted]
Jun 18 13:28:43 linux zmf-m2[3653]: ERR [Can't bind: Address already in use]

the framedeamon for the network - cam does not have that problem, which confuses my a bit, because i dont know the reason for that, ie. the difference between those 2 socks:
Jun 18 12:52:31 linux zmf-m7[3129]: INF [Debug Level = 0, Debug Log = ]
Jun 18 12:52:32 linux zmf-m7[3129]: INF [Frame server socket open, awaiting images]

system:
suse 9.0, apache 2.0.49

any ideas? i don't know why one socket can be opened, the other can't - i'm stuck... ( and still a bit of a linux newbie, sry for eventually asking a simple / stupid question, but i did not find any useful info about that.. )
thx in advance,
bjoern
User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Post by zoneminder »

Did you by any chance try running ZM as root before you ran it from the web console? If so then the zmf.sock may have been created by root and not be accessing to your web user. The simplest thing to do is stop ZM, delete zmf.sock and then restart which should fix it.

Phil,
bjoern
Posts: 2
Joined: Thu Jun 17, 2004 5:36 pm
Location: germany

Post by bjoern »

*knocks his head on the table*
of course.. i DID run the ZM daemons as root before using the webinterface. i connected the netcam later, when everything was running. so thats why the apache had no access to the first created .sock.
thanks a lot for your fast answer Phil, and thanks also for your great tool!! keep it up! :)

bjoern
Locked