[lm_ip] process issue

fabiorez · Post by **fabiorez** » Wed Jul 02, 2014 11:14 am

Hello everybody,
I'm experiencing a strange issue on a CentOS 6.3 64bit Wincc OA UI.

After stopping my project and console, seems that I cannot restart my project because of the lm_ip process, which remains alive: then I must either kill it or restart my machine.

I've already tried to manually start lm_ip with the -z option, but after starting the console I find in my Linux processes TWO lm_ip processes.

Do I have to check something in my project config file?

I'm actually using WinccOA X64 3.11 SP1 Patch 010.

Thank you in advance for your answers, kind regards,

Fabio

mpoint · Post by **mpoint** » Wed Jul 02, 2014 11:44 am

Hi,
As far as I am aware, the lm_ip process is supposed to keep running even after project shutdown. When the project starts again and the lm_ip is already (or still) running, we don't have to start a new one.

You write that you cannot restart your project. Do you get any error messages?

fabiorez · Post by **fabiorez** » Wed Jul 02, 2014 11:55 am

Hi Markus,
as I can see, the lm_ip process starts first when I open my project console.

If I stop the project, close the console and then try to re-open it, WinCC tells me that "the process monitor (WCCILpmon) of this project is not running".

In the PVSS_II.log can be found these entries

WCCOAui (0), 2014.07.02 11:10:38.561, SYS, INFO, 1, Manager Start,$
WCCOAui (0), 2014.07.02 11:49:38.705, CTRL, WARNING, 2/ctrl,
Module: PVSS 3.11
Panel: /opt/WinCC_OA/3.11/panels/projAdmin/console.pnl []
Script: Initialize
Library: /opt/WinCC_OA/3.11/scripts/libs/pmon.ctl
Line: 277: tcpWrite: Socket number (0) illegal or socket not open.
WCCOAui (0), 2014.07.02 11:49:38.705, CTRL, WARNING, 2/ctrl,
Module: PVSS 3.11
Panel: /opt/WinCC_OA/3.11/panels/projAdmin/console.pnl []
Script: Initialize
Library: /opt/WinCC_OA/3.11/scripts/libs/pmon.ctl
Line: 277: tcpWrite: Socket number (0) illegal or socket not open.

and in he console I cannot find any program listed.

Thanks

Fabio

mpoint · Post by **mpoint** » Wed Jul 02, 2014 12:01 pm

are there any log entries about why the pmon does not start? could you check whether the pmon is actually running? you could also try to start the pmon directly, maybe it will give you a more useful error message. you can start it like this: "WCCILpmon -log +stderr -proj -n".

fabiorez · Post by **fabiorez** » Wed Jul 02, 2014 12:17 pm

Thanks for the suggestion: by launching manually the PMon, I've found out that the problem was due to the SNMP default port.

After either disabling the SNMP or changing its port number (which was set at its default) I've been able to solve the problem.

Many thanks

Fabio

mkoller · Post by **mkoller** » Wed Jul 02, 2014 2:36 pm

The problem is known. It is due to the fact that the SNMP Port is inherited by the lm_ip, meaning even when Pmon stops, the lm_ip has still a reference to the open SNMP Port.

Bugs / Problems