Home > Failed To > Failed To Get Lock File /var/lock/logcheck/logcheck.lock

Failed To Get Lock File /var/lock/logcheck/logcheck.lock

OK? [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] problem with logcheck[Failed to get lockfile: /var/lock/logcheck.lock] To: debian-testing@lists.debian.org Subject: problem with logcheck[Failed to get lockfile: /var/lock/logcheck.lock] From: Prashant kumar Date: Sun, 24 Details: Failed to get lockfile: /var/lock/logcheck.lock Check temporary directory: declare -x HOME="/var/lib/logcheck" declare -x LOGNAME="logcheck" declare -x MAILTO="root" declare -x OLDPWD declare -x PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin" declare -x PWD="/var/lib/logcheck" declare -x SHELL="/bin/sh" declare Contact [EMAIL PROTECTED] Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-22 Thread Michal Sedlak Hi thank you for response This command: ps aux|grep logcheck gives only himself back root 8301 this contact form

why is it misleading? > Solution: > > you must edit the script(!) as logcheck has as security flaw > and tries to place it's lock file under /var/lock/ which is FAQ Forum Quick Links Unanswered Posts New Posts View Forum Leaders FAQ Contact an Admin Forum Community Forum Council FC Agenda Forum Governance Forum Staff Ubuntu Forums Code of Conduct Forum Given below is the mail I get from logcheck whenever it runs. But meanwhile i found others had that problem too. check my site

So the other program is blocked because of an violation of the first program... Trouble? And so you run into the same problems as with "/tmp". >> You must create a directory "logcheck" under /var/lock/ >> >> mkdir /var/lock/logcheck >> chown logcheck:logcheck /var/lock/logcheck >> chmod 755

  1. Debian distribution maintenance software pp.
  2. I am nearly sure that there is no lock file in that directory.
  3. Contact [emailprotected] -- To UNSUBSCRIBE, email to [emailprotected] with a subject of "unsubscribe".

The diff is actually against Debian's 1.2.43a. drwxr-xr-x 2 root root 4096 2004-09-24 12:39 subsys A fresh "sarge" # ls -al /var/lock drwxrwxrwt 4 root root 1024 2005-04-18 23:14 . Full text and rfc822 format available. I think 755 is fine.

I solved it with: dpkg -P logcheck apt-get install logcheck maybe apt-get --purge --reinstall install logcheck works? Full text and rfc822 format available. Message #5 received at submit@bugs.debian.org (full text, mbox, reply): From: Rainer Zocholl To: Subject: Failed to get lockfile: /var/lock/logcheck.lock Date: 17 Apr 2005 00:03:00 +0200 Package: logcheck Version: 1.2.37 https://bugs.debian.org/304978 Cheers, -- [ Todd J.

Contact listmaster@lists.debian.org Next message: Kevin Mark: "Re: How come packages dont have a homepage field?" Previous message: Adam Funk: "Re: GDM: configuring mouse pointer shape and blanking screen when not in Message #20 received at 304978@bugs.debian.org (full text, mbox, reply): From: Todd Troxell To: ralf.hildebrandt@charite.de, 304978@bugs.debian.org Subject: Re: Bug#304978: [Logcheck-devel] Bug#304978: Failed to get lockfile: /var/lock/logcheck.lock Date: Mon, 18 Apr 2005 The relevent folder/file is already chowned to the lockfile user. i try to summarize >* if /var/lock is not world writable, one should have a dir below > for one owns needs.

If you have further comments please address them to 304978@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. my response but anyway that part is clear. > -------------------------------------------------------------- > > > Maybe it would ease use a lot if "LOCKFILE" is > set in /etc/logcheck/logcheck.conf too? Acknowledgement sent to Todd Troxell : Extra info received and forwarded to list. Full text and rfc822 format available.

I think that is a very "unwanted behavior". http://1pxcare.com/failed-to/vmware-view-failed-to-lock-the-file.html Contact [EMAIL PROTECTED] Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-24 Thread Adam Funk Michal Sedlak wrote: Thank fou for response. Full text and rfc822 format available. Tags added: pending Request was from xtat to control@bugs.debian.org.

Full text and rfc822 format available. Notification sent to Rainer Zocholl : Bug acknowledged by developer. Message #29 received at 304978-close@bugs.debian.org (full text, mbox, reply): From: Todd Troxell To: 304978-close@bugs.debian.org Subject: Bug#304978: fixed in logcheck 1.2.38 Date: Tue, 19 Apr 2005 00:02:12 -0400 Source: logcheck Source-Version: http://1pxcare.com/failed-to/vmware-failed-to-lock-file.html or it's easy to block root by placing a lock file with the same name root would test when everybody can write to "/var/lock".

Contact [EMAIL PROTECTED] Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-21 Thread Michal Sedlak Hello I have problem with logcheck logchceck sends me this error message: Failed to get lockfile: /var/lock/logcheck/logcheck.lock The results of the first programs are random! Any help , TIA.

How is it related to the "declares" below?

Yamamoto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Thanks for your report. Feb 2009 logcheck Ein kleiner Test zeigt: # su -s /bin/bash -c "/usr/sbin/logcheck" logcheck ...im darauf versendeten Email: Subject: DenyHosts Report Es funktioniert!Tagged: Debian Lenny Linux Tools Ă„hnliche Artikel:IBM / Lenovo I am nearly sure that there is no lock file in that directory.

Maybe that's a wanted side effect! (But with logcheck?) How does "lock"-check reacts when it finds a lockfile not owned by the current user? nb: I've just tested this, and it's possible to disrupt logcheck runs. Trouble? his comment is here I hope if becomes more clear why it is better to created directories owned by teh "non root" lockers, and it is no good to use the sticky bit feature?

vBulletin ©2000 - 2017, Jelsoft Enterprises Ltd. Here it is on my system (on which logcheck works). $ ls -ld /var/lock/logcheck/ drwxr-xr-x 2 logcheck logcheck 4096 2005-06-24 09:02 /var/lock/logcheck/ By the way, you should learn to format your maks: * Generalise postfix rule concerning network_biopair_interop. * Add rule for ntp message about valid/infalid peers. (Closes #303661) * Improve rules .PHONY target + add checkpo rule for the translation check. Is that a bug or a feature?

Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Presumably the lock directory is now purged at startup, though I don't know what's changed. Contact [EMAIL PROTECTED] Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-23 Thread Michal Sedlak Thank fou for response.