General

Lemur Daemon does not work!

Started by neo171190 on .

Sign in or create an account to join the conversation.

11 posts

Topic starter
Hey there,
I've just downloaded Liine Lemur from the AppStore and the Editor Prog from Liine. When I'm starting Limur Daemon nothing happens. No program is running.
I have MacBook Pro 15" with Lion. I've reinstalled the Editor several times. =/
Hi,
yes i know and there must be a little icon in the task bar on top of the desktop, but there's none. However the editor program is running perfectly.
it's so weird, same installer but only one program is running =/
Hi yeah I thought it was broken too. but it runs in the background in unix terms unlike an app you won't see it as running from Dock.

But- if you open terminal you can see if it runs by typing 'ps -e|grep Daemon' like this example:
j-workstation5:~/Documents/lemur/tempest-dash js$ ps -e|grep Daemon
919 ?? 0:00.45 /Applications/Lemur Daemon.app/Contents/MacOS/Lemur Daemon -psn_0_426088


neo171190 wrote:Hi,
yes i know and there must be a little icon in the task bar on top of the desktop, but there's none. However the editor program is running perfectly.
it's so weird, same installer but only one program is running =/
Well, i've found the same line you have found with 'ps -e|grep Daemon', but sometimes i have other prgramms with 'Daemon' inside their name and it only shows one file in the terminal. =/ How can i see the whole lit
Well besides that the biggest indication of it running is that it should show the LemurDaemon
icon in the upper right of your OS X screen.

By clicking on that you can configure it's mapping and check a box to autostart after the system is booted.

[img]http://analogaccess.com/imgit/setuplemurdaemon.png[/img]

If you really need to get more specific with the ps and grep commands, you could:
ps -e|grep 'Lemur Daemon'
neo171190 wrote:Well, i've found the same line you have found with 'ps -e|grep Daemon', but sometimes i have other prgramms with 'Daemon' inside their name and it only shows one file in the terminal. =/ How can i see the whole lit
[edit]: port 8002 is Lemur editor. Daemon listens to UDP 8001.

My first guess is that another process is already bound to the Lemur Daemon port 8001.
Here's how to see your port bindings for 8001 in terminal:
netstat -an | grep 8001
udp4 0 0 *.8001 *.*

That's with the Lemur Daemon running, goes away if it isn't.

So if yours is not running, nothing should be returned for the netstat/grep command.

If you do get something, then try to figure out what is using the port.

You could check the system log and see if Lemur reports an error on startup..
grep Lemur /var/log/system.log

It's probably something simple and you'll find it! :)

-J
neo171190 wrote:Ok new status. i just looked into the process manager and saw that 'Lemur Daemon' is crashing after several seconds =/
You can find out exactly what processes are bound to ports in Terminal:
lsof -i

Port 8001 is also called 'vcom-tunnel' so if you see anything in there with vcom-tunnel than that is the process.

Here's Lemur daemon working ok:
lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
[..other process port bindings removed..]
Lemur\x20 4130 js 4u IPv4 0xffffff8015268948 0t0 UDP *:vcom-tunnel

Here's the Lemur editor running:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
[..other process port bindings removed..]
Lemur\x20 4019 js 5u IPv4 0xffffff801449f028 0t0 UDP *:57956
Lemur\x20 4019 js 6u IPv4 0xffffff80144a0d88 0t0 UDP *:63505
Lemur\x20 4019 js 8u IPv4 0xffffff801473f880 0t0 TCP j-workstation4:57956->j-workstation5:teradataordbms (ESTABLISHED)

cheers
J
First of all, thanks for your help. I'm not a mac specialist especially working with the Terminal =/ ... i tried everything you told me. nothing inside the log-file, and nothing with the port 8001. Still crashing.
You're welcome, sorry it didn't help resolve the problem.
Maybe ask Liine support?
neo171190 wrote:First of all, thanks for your help. I'm not a mac specialist especially working with the Terminal =/ ... i tried everything you told me. nothing inside the log-file, and nothing with the port 8001. Still crashing.