Webdirectory fills with large number of core.nnnn files.

[Paul]

Dear All,

I ran into the following problem. After starting ZM the directory /usr/lib/zm/html is being filled with core.nnnnn files (around 30000 files of 139MB each!) until resources are depleted. I deleted the files and restarted ZM without problems, but after a while the proces started again. Have no clue why this happens.

Any suggestions?

Thanks and with kind regards,

Paul

[cordel]

Those are core dump files and I think they are created by gdb and used for debuging.
Unfortunatly thats all I know. Did you use gdb to start zm?

Corey

[zoneminder]

Yes, these are core files. They are often the result of processing crashing, is there anything in your amdc.log or messages log to suggest if this is happening?

[Paul]

Dear Phil and Corey,

Thanks for you reply. Before I forget, some specs: Fedora core 3, ZM v.1.21.4 on a Pentium 1.8 Ghz, 256Mb Ram.

I checked the messages log and found a long list of the same errors. Just a chunk of it:

Jan 7 21:06:21 munters zmc_m1[25148]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:06:21 munters zmc_m1[25148]: INF [Starting Capture]
Jan 7 21:06:22 munters zma_m1[25156]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:06:22 munters zma_m1[25156]: WAR [Waiting for capture daemon]
Jan 7 21:06:23 munters zma_m1[25156]: INF [Warming up]
Jan 7 21:06:26 munters zmc_m1[25148]: ERR [Select timed out]
Jan 7 21:06:33 munters zmc_m1[25148]: INF [Got TERM signal, exiting]
Jan 7 21:06:33 munters zmc_m1[25148]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:06:33 munters zmc_m1[25175]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:06:33 munters zmc_m1[25175]: INF [Starting Capture]
Jan 7 21:06:47 munters zmc_m1[25175]: ERR [Select timed out]
Jan 7 21:06:53 munters zmc_m1[25175]: INF [Got TERM signal, exiting]
Jan 7 21:06:53 munters zmc_m1[25175]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:06:54 munters zmc_m1[25220]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:06:54 munters zmc_m1[25220]: INF [Starting Capture]
Jan 7 21:07:08 munters zmc_m1[25220]: ERR [Select timed out]
Jan 7 21:07:14 munters zmc_m1[25220]: INF [Got TERM signal, exiting]
Jan 7 21:07:14 munters zmc_m1[25220]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:07:14 munters zmc_m1[25256]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:07:16 munters zmc_m1[25256]: INF [Starting Capture]
Jan 7 21:07:29 munters zmc_m1[25256]: ERR [Select timed out]
Jan 7 21:07:35 munters zmc_m1[25256]: INF [Got TERM signal, exiting]
Jan 7 21:07:35 munters zmc_m1[25256]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:07:35 munters zmc_m1[25279]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:07:36 munters zmc_m1[25279]: INF [Starting Capture]
Jan 7 21:07:50 munters zmc_m1[25279]: ERR [Select timed out]
Jan 7 21:07:55 munters zmc_m1[25279]: INF [Got TERM signal, exiting]
Jan 7 21:07:55 munters zmc_m1[25279]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:07:55 munters zmc_m1[25297]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:07:56 munters zmc_m1[25297]: INF [Starting Capture]
Jan 7 21:08:09 munters zmc_m1[25297]: ERR [Select timed out]
Jan 7 21:08:16 munters zmc_m1[25297]: INF [Got TERM signal, exiting]
Jan 7 21:08:16 munters zmc_m1[25297]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:08:16 munters zmc_m1[25333]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:08:16 munters zmc_m1[25333]: INF [Starting Capture]
Jan 7 21:08:30 munters zmc_m1[25333]: ERR [Select timed out]
Jan 7 21:08:36 munters zmc_m1[25333]: INF [Got TERM signal, exiting]
Jan 7 21:08:36 munters zmc_m1[25333]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:08:37 munters zmc_m1[25374]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:08:37 munters zmc_m1[25374]: INF [Starting Capture]
Jan 7 21:08:46 munters zmc_m1[25374]: INF [Got TERM signal, exiting]
Jan 7 21:08:46 munters zmc_m1[25374]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:08:46 munters zma_m1[25156]: INF [Got signal (Terminated), exiting]
Jan 7 21:09:00 munters zmu[25461]: ERR [Shared memory not initialised by capture daemon]
Jan 7 21:09:01 munters zmc_m1[25469]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:09:01 munters zmc_m1[25469]: INF [Starting Capture]
Jan 7 21:09:01 munters zma_m1[25473]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:09:01 munters zma_m1[25473]: WAR [Waiting for capture daemon]
Jan 7 21:09:02 munters zma_m1[25473]: WAR [Waiting for capture daemon]
Jan 7 21:09:03 munters zma_m1[25473]: INF [Warming up]
Jan 7 21:09:06 munters zmc_m1[25469]: ERR [Select timed out]
Jan 7 21:09:31 munters zmc_m1[25469]: ERR [Select timed out]
Jan 7 21:09:44 munters zmc_m1[25469]: INF [Got TERM signal, exiting]
Jan 7 21:09:44 munters zmc_m1[25469]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:09:48 munters zmc_m1[25585]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:09:51 munters zmc_m1[25585]: INF [Starting Capture]
Jan 7 21:09:55 munters zmc_m1[25585]: ERR [Select timed out]
Jan 7 21:10:08 munters zmc_m1[25585]: INF [Got TERM signal, exiting]
Jan 7 21:10:08 munters zmc_m1[25585]: ERR [Can't connect to remote camera: Interrupted system call]
Jan 7 21:10:09 munters zmc_m1[25611]: INF [Debug Level = 0, Debug Log = <none>]
Jan 7 21:10:10 munters zmc_m1[25611]: INF [Starting Capture]
Jan 7 21:10:14 munters zmc_m1[25611]: ERR [Select timed out]
Jan 7 21:10:19 munters zmc_m1[25611]: INF [Got TERM signal, exiting]
Jan 7 21:10:19 munters zmc_m1[25611]: ERR [Can't connect to remote camera: Interrupted system call]


Any idea what causes the process to crash all the time?

Thanks in advance and kind regards,

Paul

[zoneminder]

It looks like zmc can't actually connect to your camera. Can you give some more details of the settings you are using for your monitor?

[Paul]

Dear Phil,

I copied this from an earlier posting concerning the low FPS rate I got with ZM .

I am running ZM v.1.21.4 on a Pentium 1.8Ghz (256MB memory) connected to one Sitecom IP network camera, and ran into 2 problems.

Although the camera supports 640*480, I could not get this working with ZM. The source item turnes red, and when opening the stream it says "Failed to connect to server. Acces Denied". This did not happen when using 320*240 size. I was the referred to an earlier topic by Tux and adjusted the memory settings, which solved this issue. By adjusting both the parameters kernel.shmall (128 Mb) and kernel.shmmax (196Mb) from /etc/sysctl.conf, I now can also use the 640*480 size.

It did however not solve the low FPS rate, not in 640*480 nor in 320*240. Even at size 320*240 the framerate is low as 1 fps or less. It used to be up to over 15 when using a USB (philips) webcam. In vain I tried all kinds of changes at the side of the camera (higher/lower compression, fixed/automatic framerates) and on the ZM side (http 1.1/1.0, ZM_HTTP_TIMEOUT, regexpres, jpg/mpg). With the mpg option the screen blanks or on rare occasions pops-up and freezes.

Further I tried to run zmc -m 1, but the zmc file is not found, although it clearly exists in the /usr/lib/zm/bin directory.

Lastly, the monitor dies after a while. The /var/log/message is:

Dec 30 23:17:04 munters zmc_m1[30226]: INF [Got TERM signal, exiting]
Dec 30 23:17:04 munters zmc_m1[30226]: ERR [Can't connect to remote camera: Interrupted system call]
Dec 30 23:17:04 munters zmc_m1[30334]: INF [Debug Level = 0, Debug Log = <none>]
Dec 30 23:17:05 munters zmc_m1[30334]: INF [Starting Capture]
Dec 30 23:17:23 munters zmc_m1[30334]: ERR [Select timed out]

This is still unsolved, and since working on 640*480 I get into trouble with these crashes and core. file dumps.

Still no clue why this happends, and hoping anyone knows a solution.

Many thanks for the support sofar and with kind regards,

Paul

[cordel]

The rate that you can capture from a web cam depends on the method you use to get the image and the ability of the camera and the quality of your network (more relevant to wireless as wired don't suffer from interference).

ZM will not capture an mpg image, only jpeg and mjpeg. If you are capturing a single jpeg at a time, it is slower than capturing a mjpeg stream as the request has to go out for each jpeg snapshot. If the camera supports mjpeg it would be better to use that and limit the fps from the camera. The error your seeing there is most likely that zm is timing out waiting for the image to be returned from the camera and maybe requesting at a rate that the camera can't keep up with and zm times out waiting for it.

A usb cam is different than a network cam as the images are retrieved from the buffer and not over the network so what you web cam can do is not relevant to your net cam.

[zoneminder]

What are the remote host paths etc you are using for the Sitecom camera?

Also can you do a wget at both resolutions and if so, time how long it takes?

[Paul]

Dear Phil and Cordel,

Thanks for your inputs sofar and sorry for my late reply.

The following settings are being used:

Source Type:Remote
Remote Host Name: camera:xxxxxx@10.0.0.136
Remote Host Port:9294
Remote Host Path:IMAGE.JPG
Remote Image Colours: 24 bit colour
Capture Width (pixels):640
Capture Height (pixels):480


In vain I tried all kinds of changes at the side of the camera (higher/lower compression, fixed/automatic framerates) and on the ZM side (http 1.1/1.0, diffrent ZM_HTTP_TIMEOUT, regexpres, jpg/mpg). With the mpg option the screen blanks. I must admit that I don't understand exactly how to set the camera and ZM at the "mjpeg" mode. Further, I do not understand what Phil means by doing "wget". Also I have seen some remarks on using "cgi-bin" in the settings, but I do not know how to and whether this also works with this type of camera. I have only limited linux experience as you might have guest, so any help is ofcourse highly appreciated.

With kind regards,

Paul

[cordel]

If you have the documentation or better yet know of an online source (so we could have a look) this would help a bit.

What you may do is open the camera in a firefox browser. Move your curser on top of the streaming image, right click, and select "properties".

What we are interested in is the Location, Width, and Height (mostly the location).

Also, I noticed you put your password for the cam in, and while it's a private address and I don't know if you just overlooked it, I'm going to edit your post and X it out.

wget is a program in linux sort of like ftp. You can use it to capture the stream to a file and use [ctrl] - [c] to interupt it. You can also use ngrep and do the same thing if it is included in your distro.

Regards,
Corey

[Paul]

Dear Cordel,

Thanks your reply and particularly for X-ing out the user and password details.

I followed your instructions and got the properties in firefox:

Location:
http://munters.xs4all.nl/cgi-bin/zm/zms ... 1137878790
Width: 640 px
Height: 480 px

I then used the above location with wget, which gave me following result:


[root@munters ~]# wget
http://munters.xs4all.nl/cgi-bin/zm/zms ... 1137879396
[1] 11172
[2] 11173
[3] 11174
[4] 11175
[5] 11176
--22:46:53-- http://munters.xs4all.nl/cgi-bin/zm/zms?mode=jpeg
=> `zms?mode=jpeg'
Resolving munters.xs4all.nl... [root@munters ~]# 213.84.28.90
Connecting to munters.xs4all.nl|213.84.28.90|:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
22:46:53 ERROR 500: Internal Server Error.

It hangs here, so I give crtl-c

[1] Exit 1 wget
http://munters.xs4all.nl/cgi-bin/zm/zms?mode=jpeg
[2] Done monitor=1
[3] Done scale=100
[4]- Done maxfps=30
[5]+ Done auth=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Does this ring a bell?
Many thanks and kind regards,

Paul

[cordel]

Hi Paul,
Sorry I didn't explain good enough, but the details I was looking for were for the camera it self and not the camera through zm.

If you open the camera directly in a web browser and check the properties what do you get?

Regards,
Corey

[cordel]

Hi Paul,
You might want to read through the manual for your camera. I skimmed through it and get the impression that it only streams to activex enabled browsers (IE) and does not support mjpeg. Since ZM can not get streams via this method (only mjpeg at this time), the best you can do is do jpeg grabs which as you might expect will produce a low frame rate.
The manual is here http://www.sitecom.com/drivers_result.p ... ductid=299

Regards,
Corey

[Paul]

Dear Corey,

Thanks for the reply. The properties are:

http://10.0.0.136/IMAGE.JPG?cidx=2004114937272504

I could not do a wget because I need to pass the username and password, and do not know how to do this. But reading the document you referred to made me realise that higher FPS will most probably be not possible, although I do get 5FPS/s with a java applet. The webinterface of that shows the monitor with JAVA contains the following applet reference:

<APPLET name="cvcs" CODEBASE="http://10.0.0.136:80/" CODE="xplug.class" WIDTH=640 HEIGHT=480>
<param name="RemotePort" value=80>
<param name="Timeout" value=5000>
<param name="RotateAngle" value=0>
<param name="PreviewFrameRate" value=2>
<param name="DeviceSerialNo" value="Y2FtZXJhOmJlZWxkaWc=">
</APPLET>

Would it be possible to include this somewhere in ZM?

Many thanks and kind regards,

Paul

[zoneminder]

Dear Corey,

Thanks for the reply. The properties are:

http://10.0.0.136/IMAGE.JPG?cidx=2004114937272504

I could not do a wget because I need to pass the username and password, and do not know how to do this.

If your camera uses basic authentication, which a lot do, then passing username and password via wget is like this

Code: Select all

wget 'http://username:password@10.0.0.136/IMAGE.JPG?cidx=2004114937272504'