Author Topic: AVAST - pidfile: Another instance is already running  (Read 941 times)

0 Members and 1 Guest are viewing this topic.

Offline MagicPeter

  • Newbie
  • *
  • Posts: 3
AVAST - pidfile: Another instance is already running
« on: January 16, 2024, 06:54:27 PM »
Moin,
ich nutzt PMG 8.011 seit ein paar Monaten.
Heute habe ich nach der Anleitung
https://pmg.proxmox.com/wiki/index.php/Install_Avast
Avast 4.4 als 2ten Virenscanner installiert.
Erst eine Lizenz gekauft und dann installiert.
Funktionierte wirklich sehr einfach.

Betriebsystem: Debian 12

Leider scheint das nicht ganz funktioniert zu haben.

Es erscheint ein Fehler im Log:

Jan 16 18:00:16 pmg avast[965]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:00:16 pmg avast[965]: main: Fatal error. Exiting.

Wir kann ich das beheben?

Auch der Befehl scan /etc zeigt keine Rückmeldung.

ein scan -h bringt eine Übersicht der Syntax

ein avast -h zeigt auch wieder

Jan 16 18:00:16 pmg avast[965]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:00:16 pmg avast[965]: main: Fatal error. Exiting.

an

Was mache ich falsch?

journalctl | grep -i avast -C 3

Jan 16 18:00:16 pmg avast[965]: main: Starting Avast 4.4.0
Jan 16 18:00:16 pmg avast[965]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:00:16 pmg avast[965]: main: Fatal error. Exiting.
Jan 16 18:00:22 pmg postfix/postscreen[951]: CONNECT from [183.165.251.103]:63720 to [192.168.30.123]:25
Jan 16 18:00:28 pmg postfix/postscreen[951]: PASS NEW [183.165.251.103]:63720
Jan 16 18:00:28 pmg postfix/smtpd[967]: connect from unknown[183.165.251.103]
--
Jan 16 18:01:01 pmg pmgpolicy[954]: defer greylisted mail
Jan 16 18:01:01 pmg postfix/smtpd[967]: NOQUEUE: reject: RCPT from renaissanitory.com[136.144.147.211]: 450 4.7.1 <ccc@jianghai-europe.com>: Recipient address rejected: Service is unavailable (try later); from=<sdfsdf@germanchises.com> to=<ccc@jianghai-europe.com> proto=ESMTP helo=<germanchises.com>
Jan 16 18:01:01 pmg postfix/smtpd[967]: disconnect from renaissanitory.com[136.144.147.211] ehlo=1 mail=1 rcpt=0/1 quit=1 commands=3/4
Jan 16 18:01:19 pmg systemd[1]: Starting avast-vpsupdate.service - Update Avast virus database...
Jan 16 18:01:19 pmg vpsupdate[975]: Connecting to repository http://linux-av.u.avcdn.net/linux-av/avast/x86_64/vps9
Jan 16 18:01:19 pmg vpsupdate[975]: Current VPS version: 24011606
Jan 16 18:01:19 pmg vpsupdate[975]: VPS is up to date.
Jan 16 18:01:19 pmg vpsupdate[982]: 2024-01-16 18:01:19.350753+0100 [ 982: 3d6] INFO Submit: Burger V3 sent
Jan 16 18:01:19 pmg /usr/lib/avast/submit[982]: Submit: Burger V3 sent
Jan 16 18:01:19 pmg systemd[1]: avast-vpsupdate.service: Deactivated successfully.
Jan 16 18:01:19 pmg systemd[1]: Finished avast-vpsupdate.service - Update Avast virus database.
Jan 16 18:01:19 pmg postfix/postscreen[951]: CONNECT from [183.165.251.103]:65347 to [192.168.30.123]:25
Jan 16 18:01:19 pmg postfix/postscreen[951]: PASS OLD [183.165.251.103]:65347
Jan 16 18:01:19 pmg postfix/smtpd[967]: connect from unknown[183.165.251.103]
--
Jan 16 18:13:47 pmg pmg-smtp-filter[877]: Killing "1" children
Jan 16 18:15:12 pmg pmgpolicy[878]: starting policy database maintenance (greylist, rbl)
Jan 16 18:15:12 pmg pmgpolicy[878]: end policy database maintenance (9 ms, 1 ms)
Jan 16 18:15:16 pmg avast[1115]: main: Starting Avast 4.4.0
Jan 16 18:15:16 pmg avast[1115]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:15:16 pmg avast[1115]: main: Fatal error. Exiting.
Jan 16 18:15:37 pmg avast[1118]: main: Starting Avast 4.4.0
Jan 16 18:15:37 pmg avast[1118]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:15:37 pmg avast[1118]: main: Fatal error. Exiting.
Jan 16 18:15:37 pmg pmg-smtp-filter[877]: starting database maintenance
Jan 16 18:15:37 pmg pmg-smtp-filter[877]: end database maintenance (4 ms)
Jan 16 18:15:40 pmg avast[1121]: main: Starting Avast 4.4.0
Jan 16 18:15:40 pmg avast[1121]: pidfile: Another instance is already running; /run/avast/avast.pid is locked
Jan 16 18:15:40 pmg avast[1121]: main: Fatal error. Exiting.
Jan 16 18:15:41 pmg postfix/postscreen[1122]: CONNECT from [113.87.122.18]:30133 to [192.168.30.123]:25
Jan 16 18:15:41 pmg postfix/postscreen[1122]: PASS OLD [113.87.122.18]:30133
Jan 16 18:15:41 pmg postfix/smtpd[1123]: connect from unknown[113.87.122.18]
root@pmg:/#
« Last Edit: January 16, 2024, 06:58:56 PM by MagicPeter »

Offline MagicPeter

  • Newbie
  • *
  • Posts: 3
Re: AVAST - pidfile: Another instance is already running
« Reply #1 on: January 16, 2024, 07:19:14 PM »
####

Ich habe dann mal das PID-File gelöscht

cd /run/avast/
cat avast.pid | xargs kill

und siehe da die Fehlermeldung kommt nicht mehr und

avast -v funktioinert

ABER ;)

Nach einen REBOOT ist das PID-File (avast.pid) wieder da.

Problem also noch nicht gelöst...

Hat jemand noch eine Idee?

Offline MagicPeter

  • Newbie
  • *
  • Posts: 3
Re: AVAST - pidfile: Another instance is already running
« Reply #2 on: January 17, 2024, 08:46:24 AM »
Moin,
es sieht aber so aus als wenn der Avast Scanner funktioniert.
Heute im Logfile gefunden:

Jan 17 00:39:21 pmg pmg-smtp-filter[915]: 2029B65A713A9438D8: virus detected: HTML:RedirBA-inf [Trj] (avast)
Jan 17 00:39:26 pmg pmg-smtp-filter[915]: WARNING: check: dns_block_rule RCVD_IN_ZEN_BLOCKED_OPENDNS hit, creating /root/.spamassassin/dnsblock_zen.spamhaus.org (This means DNSBL blocked you due to too many queries. Set all affected rules score to 0, or use "dns_query_restriction deny zen.spamhaus.org" to disable queries)
Jan 17 00:39:26 pmg pmg-smtp-filter[915]: WARNING: check: dns_block_rule URIBL_BLOCKED hit, creating /root/.spamassassin/dnsblock_multi.uribl.com (This means DNSBL blocked you due to too many queries. Set all affected rules score to 0, or use "dns_query_restriction deny multi.uribl.com" to disable queries)
Jan 17 00:39:26 pmg pmg-smtp-filter[915]: 2029B65A713A9438D8: SA score=18/5 time=5.153 bayes=1.00 autolearn=spam autolearn_force=no hits=BAYES_99(3.5),BAYES_999(0.2),CBJ_GiveMeABreak(1.75),DMARC_QUAR(0.1),GB_SUBJ25(0.5),HTML_FONT_LOW_CONTRAST(0.001),HTML_MESSAGE(0.001),KAM_DMARC_QUARANTINE(3),KAM_DMARC_STATUS(0.01),NORDNS_LOW_CONTRAST(0.071),POISEN_SPAM_PILL(0.1),POISEN_SPAM_PILL_1(0.1),RCVD_IN_BL_SPAMCOP_NET(1.347),RCVD_IN_MSPIKE_BL(0.001),RCVD_IN_MSPIKE_L5(0.001),RCVD_IN_PSBL(2.7),RCVD_IN_VALIDITY_RPBL(1.31),RCVD_IN_ZEN_BLOCKED_OPENDNS(0.001),RDNS_NONE(0.793),SPF_HELO_NONE(0.001),SPF_SOFTFAIL(0.665),T_SCC_BODY_TEXT_LINE(-0.01),URIBL_ABUSE_SURBL(1.25),URIBL_BLOCKED(0.001),URIBL_DBL_BLOCKED_OPENDNS(0.001),URIBL_PH_SURBL(0.61)
--
Jan 17 00:43:31 pmg postfix/smtpd[2932]: disconnect from unknown[43.163.245.24] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 17 00:43:31 pmg pmg-smtp-filter[2191]: 2024/01/17-00:43:31 CONNECT TCP Peer: "[127.0.0.1]:55060" Local: "[127.0.0.1]:10024"
Jan 17 00:43:31 pmg pmg-smtp-filter[2191]: 2029B65A714A374623: new mail message-id=<a2bfbb29001453635f1157971008841f@uber.com>
Jan 17 00:43:31 pmg pmg-smtp-filter[2191]: 2029B65A714A374623: virus detected: HTML:RedirBA-inf [Trj] (avast)

Laut PMG wurden 3 Viren von avast gefunden und entfernt.