Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: HELP Secunia cannot scan and psia log filled with errors

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI

This thread has been marked as locked.
mikeysrealm HELP Secunia cannot scan and psia log filled with errors
Member 1st Jan, 2013 23:37
Ranking: 0
Posts: 5
User Since: 1st Jan, 2013
System Score: N/A
Location: US
Last edited on 2nd Jan, 2013 03:18

Secunia 2.0 stopped scanning my windows pc on the 19th of December. even selecting the "scan now" did nothing. I just uninstalled 2.0 and installed 3.0, and I tail the log file and see that "psialog.txt" is filled with continual errors. I am running windows 7 64 bit. The scan has been running for over 15 minutes now and it just reports "updating scanning results". Here is a sample of the errors in the logs (these are continual & repeating):

[01/01 17:37:19.235] Unknown name in invoke:periodic
[01/01 17:37:19.235] Unknown name in invoke:QueryState
[01/01 17:37:19.285] Unknown name in invoke:QueryState
[01/01 17:37:19.385] Unknown name in invoke:QueryState
[01/01 17:37:19.485] Unknown name in invoke:QueryState
[01/01 17:37:19.585] Unknown name in invoke:QueryState
[01/01 17:37:19.685] Unknown name in invoke:QueryState
[01/01 17:37:19.735] Unknown name in invoke:periodic
[01/01 17:37:19.735] Unknown name in invoke:QueryState
[01/01 17:37:19.785] Unknown name in invoke:QueryState
[01/01 17:37:19.885] Unknown name in invoke:QueryState
[01/01 17:37:19.985] Unknown name in invoke:QueryState
[01/01 17:37:20.085] Unknown name in invoke:QueryState
[01/01 17:37:20.185] Unknown name in invoke:QueryState
[01/01 17:37:20.235] Unknown name in invoke:periodic
[01/01 17:37:20.235] Unknown name in invoke:QueryState
[01/01 17:37:20.285] Unknown name in invoke:QueryState
[01/01 17:37:20.385] Unknown name in invoke:QueryState
[01/01 17:37:20.485] Unknown name in invoke:QueryState
[01/01 17:37:20.585] Unknown name in invoke:QueryState
[01/01 17:37:20.685] Unknown name in invoke:QueryState
[01/01 17:37:20.735] Unknown name in invoke:periodic
[01/01 17:37:20.735] Unknown name in invoke:QueryState
[01/01 17:37:20.785] Unknown name in invoke:QueryState
[01/01 17:37:20.885] Unknown name in invoke:QueryState
[01/01 17:37:20.985] Unknown name in invoke:QueryState

Additional update - it is 4 hours later and secunia is still "Scanning for outdated programs: updating scanning results". I again tail -f 'ed the logs and the same errors are occurring continually. if I grep out those errors, I get the following additional log entries:

[01/01 21:16:22.134] Checking in with server (psi3.secunia.com)
[01/01 21:16:22.134] Connecting to psi3.secunia.com:443
[01/01 21:16:22.134] GET /psi_api/3006/?action=agent_check&agent_version=3. 0.0.6001&tz=18000&fm=0x80000000&uid=kn0m7BfWteec1f fd1f9e117d33597247xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx &ui=agent&langroup=WORKGROUP&host=SYX01
[01/01 21:16:22.135] Request timeouts : 60000ms, 30000ms, 30000ms
[01/01 21:16:22.488] Connection error. Trying direct connection.
[01/01 21:16:22.489] Error in HttpRequest: status=499, statusText='It was not possible to connect to the revocation server or a definitive response could not be obtained.',winCode=12057
[01/01 21:16:22.634] Error while checking in with server (12057) : "It was not possible to connect to the revocation server or a definitive response could not be obtained."
[01/01 21:16:22.634] -- Program Configuration --
-- Internal variables --
Version 3.0.0.6001
BinPath C:\Program Files (x86)\Secunia\PSI\PSIA.exe
BinDir C:\Program Files (x86)\Secunia\PSI
APPNAME Secunia PSI Agent
BINNAME psi.exe
-- Logging Settings --
LogLevel 2
LogFile C:\Program Files (x86)\Secunia\PSI\psialog.txt
LogFileMax 2097152
-- UserId options --
CAUser kn0m7BfWteec1ffd1f9e117d33597247xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxx
-- Scan options --
ScanType 2
CheckOSUpdates 1
-- Customer Area options --
GroupName
-- Network Configuration --
API_SERVER_HOST psi3.secunia.com
API_SERVER_PORT 443
API_BASE_URI /psi_api/3006/?
-- Connectivity Options: --
RequestTimeout 120
NetworkImplementation WinInet
-- Proxy options --
ProxyURL
ProxyUser
ProxyPass <Not Set>
ProxyConfigState 0
-- Security options --
IgnoreInvalidCN 0
IgnoreUnknownCA 0
IgnoreCertRevocation 0
-- Service options --
InstallService 0
StartService 1
RemoveService 0
RunAsUser
RunAsPass <Not Set>
RunAsLocalSystem 0
DontWriteRegistry 0
Foreground 0
-- Computer Information --
ComputerName SYX01
LanGroup WORKGROUP
CurrentUser SYSTEM
UserPrincipalName
-- CheckIn Information --
CheckInInterval 60
LastCheckIn 01/01/13 21:16:22
NextInspection 01/01/13 17:15:59
ServerTime 01/01/80 00:00:00
REG_KEY_PATH SOFTWARE\Secunia\PSIA
RegConfKey HKEY_LOCAL_MACHINE

This appears to also be repeated...

mogs RE: HELP Secunia cannot scan and psia log filled with errors
Expert Contributor 2nd Jan, 2013 09:49
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
@mikevsrealm

Hello.

It might have been better to have reported your issue prior to installing psi 3.0.
Sometimes a setting gets altered.....have you changed your AV ?
Did you let the new install remove the previous version ?
Try reverting back to the version that you know was working until recently ...but before running....go thro' the settings in the FAQ's thoroughly...here :-
http://secunia.com/vulnerability_scanning/personal...

Hope it helps......regards......

--
Was this reply relevant?
+0
-0
mikeysrealm RE: HELP Secunia cannot scan and psia log filled with errors
Member 2nd Jan, 2013 15:24
Score: 0
Posts: 5
User Since: 1st Jan 2013
System Score: N/A
Location: US
Note that as of this morning it is still hung on Scanning for outdated programs Updating scanning results. The older version stopped working, so I went to the most recent version,. which did fully uninstall the 2.x version prior to installing.

None of the troubleshooting tips on the FAQ apply to this situation - they don't discuss what to do when PSI is NOT working at all - unable to scan. I thought that providing the ERRORS FROM THE LOGS would be the best bet, how can we find what these errors mean?

In case the errors are due to the inability to communicate with psi3.secunia.com, I further reviewed the logs, the DNS set up for psi3.secunia.com (the dns name in the logs), and the error codes (winCode=12057 and HTTP 499). HTTP 499 is a custom error code, but wincode 12057 is related to the certificate - the inability to validate the certificate via the revocation server. I ran openssl s_client to both servers in the DNS resolution for psi3.secunia.com:

;; ANSWER SECTION:
psi3.secunia.com. 586 IN A 91.198.117.181
psi3.secunia.com. 586 IN A 91.198.117.182

and found that they have different server certificates. 182 has:
Server certificate
subject=/1.3.6.1.4.1.311.60.2.1.3=DK/businessCateg ory=Private Organization/O=Secunia ApS/serialNumber=ApS305139/C=DK/ST=
Copenhagen/L=Copenhagen/OU=PSI3/CN=psi3.secunia.co m
issuer=/C=US/O=thawte, Inc./OU=Terms of use at https://www.thawte.com/cps (c)06/CN=thawte Extended Validation SSL CA

and 181 has:
Server certificate
subject=/O=psi3.secunia.com/OU=Go to https://www.thawte.com/repository/index.html/OU=Th... SSL123 certificate/OU=Domain
Validated/CN=psi3.secunia.com
issuer=/C=US/O=Thawte, Inc./OU=Domain Validated SSL/CN=Thawte DV SSL CA

But I was able to download and read both CRL's listed in the server certificates, so either this is an error related to one of the intermediate ssl certificate (I have yet to check) or not an issue at all. Furthermore if I issue a WGET for the SAME URL that is in the logs, I do get an HTTP error:

--2013-01-02 09:20:16-- https://psi3.secunia.com/psi_api/3006/?action=agen...
0x80000000&uid=kn0m7BfWteec1ffd1f9e117d33597247xxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxx&ui=agent&langroup=WO RKGROUP&host=SYX01
Resolving psi3.secunia.com... 91.198.117.182, 91.198.117.181
Connecting to psi3.secunia.com|91.198.117.182|:443... connected.
WARNING: cannot verify psi3.secunia.com's certificate, issued by `/C=US/O=Thawte, Inc./OU=Domain Validated SSL/CN=Thawte
DV SSL CA':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response...
HTTP/1.1 406 Not Found
Date: Wed, 02 Jan 2013 14:21:25 GMT
Server: Apache
X-Powered-By: PHP/5.3.3
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8
2013-01-02 09:20:16 ERROR 406: Not Found.

To install the latest 2.x version of PSI, where would I get it from the Secunia site? The only download that I found was for the 3.x version?

Thanks,

Mike
Was this reply relevant?
+0
-0
Maurice Joyce RE: HELP Secunia cannot scan and psia log filled with errors
Handling Contributor 2nd Jan, 2013 16:36
Score: 11792
Posts: 9,036
User Since: 4th Jan 2009
System Score: N/A
Location: UK
Mike,
To install the latest 2.x version of PSI, where would I get it from the Secunia site? The only download that I found was for the 3.x version?

Details are below my Signature Block.


--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+0
-0
mikeysrealm RE: HELP Secunia cannot scan and psia log filled with errors
Member 2nd Jan, 2013 23:48
Score: 0
Posts: 5
User Since: 1st Jan 2013
System Score: N/A
Location: US
Same issue now that I have downgraded to 2.0. Just like before I upgraded, I select SCAN, and after a few seconds a small window pops up saying scan aborted. Below is the paste of the tail of the psialog, at 17:40:32 is when I selected the "scan" icon. At 17:40:54 js when I was informed that the scan was aborted (without any action on my part). After this, the scan icon no longer does anything. I have posted a screen shot of the aborted scan alert here:

http://goo.gl/qUzUf

Thanks,

Mike

Log extract:
[01/02 17:40:28.911] Unknown name in invoke:periodic
[01/02 17:40:29.411] Unknown name in invoke:periodic
[01/02 17:40:29.911] Unknown name in invoke:periodic
[01/02 17:40:30.411] Unknown name in invoke:periodic
[01/02 17:40:30.911] Unknown name in invoke:periodic
[01/02 17:40:31.411] Unknown name in invoke:periodic
[01/02 17:40:31.911] Unknown name in invoke:periodic
[01/02 17:40:32.411] Unknown name in invoke:periodic
[01/02 17:40:32.911] Checking in with server (psi.secunia.com)
[01/02 17:40:32.911] Connecting to psi.secunia.com:443
[01/02 17:40:32.911] GET /psi_api/2003/?type=agent_check&agent_version=&tz= 18000&fm=0x80000000&uid=kn0m7BfWteec1ffd1f9e1
17d33597247xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&ui=age nt&langroup=WORKGROUP&host=SYX01
[01/02 17:40:32.911] Request timeouts : 60000ms, 30000ms, 30000ms
[01/02 17:40:52.753] Error in HttpRequest: status=499, statusText='It was not possible to connect to the revocation serv
er or a definitive response could not be obtained.
',winCode=12057
[01/02 17:40:52.912] Error while checking in with server (12057) : "It was not possible to connect to the revocation ser
ver or a definitive response could not be obtained."
[01/02 17:40:52.912] -- Program options --
[01/02 17:40:52.912] Version 0
[01/02 17:40:52.912] LogLevel 2
[01/02 17:40:52.912] Help 0
[01/02 17:40:52.912] CLI 0
[01/02 17:40:52.912] CLICLI 0
[01/02 17:40:52.912] Foreground 0
[01/02 17:40:52.912] InstallService 0
[01/02 17:40:52.912] StartService 1
[01/02 17:40:52.912] RemoveService 0
[01/02 17:40:52.912] RunAsUser
[01/02 17:40:52.912] RunAsPass <Not Set>
[01/02 17:40:52.913] RunAsLocalSystem 0
[01/02 17:40:52.913] DontWriteRegistry 0
[01/02 17:40:52.913] Network Appliance 0
[01/02 17:40:52.913] GUID
[01/02 17:40:52.913] -- Scan options --
[01/02 17:40:52.913] ScanType 1
[01/02 17:40:52.913] CheckWinUpdates 1
[01/02 17:40:52.913] -- Service options --
[01/02 17:40:52.913] CheckInInterval 60
[01/02 17:40:52.913] RequestTimeout 120
[01/02 17:40:52.913] -- Customer Area options --
[01/02 17:40:52.913] GroupName
[01/02 17:40:52.913] CAUser kn0m7BfWteec1ffd1f9e117d33597247xxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxx
[01/02 17:40:52.913] -- Internal variables --
[01/02 17:40:52.913] BinPath C:\Program Files (x86)\Secunia\PSI\PSIA.exe
[01/02 17:40:52.913] BinDir C:\Program Files (x86)\Secunia\PSI
[01/02 17:40:52.914] API_SERVER_HOST psi.secunia.com
[01/02 17:40:52.914] API_SERVER_PORT 443
[01/02 17:40:52.914] API_BASE_URI /psi_api/2003/?
[01/02 17:40:52.914] APPNAME Secunia PSI Agent
[01/02 17:40:52.914] BINNAME psi.exe
[01/02 17:40:52.914] REG_KEY_PATH SOFTWARE\Secunia\PSIA
[01/02 17:40:52.914] RegConfKey HKEY_LOCAL_MACHINE
[01/02 17:40:52.914] Version
[01/02 17:40:52.914] ComputerName SYX01
[01/02 17:40:52.914] LanGroup WORKGROUP
[01/02 17:40:52.914] CurrentUser SYSTEM
[01/02 17:40:52.914] UserPrincipalName
[01/02 17:40:52.914] LogFile C:\Program Files (x86)\Secunia\PSI\psialog.txt
[01/02 17:40:52.914] LogFileMax 2097152
[01/02 17:40:52.914] OptionMask 1024
[01/02 17:40:52.914] LastCheckIn 01/02/13 17:40:32
[01/02 17:40:52.914] NextInspection 01/02/13 17:39:29
[01/02 17:40:52.914] ServerTime 01/01/80 00:00:00
[01/02 17:40:52.915] Unknown name in invoke:notifyCheckin
[01/02 17:40:52.915] Unknown name in invoke:periodic
[01/02 17:40:52.915] Starting new inspection (type=1)
[01/02 17:40:52.915] Starting Windows Update inspection
[01/02 17:40:52.915] Downloading software inspection rules from server
[01/02 17:40:52.915] Connecting to psi.secunia.com:443
[01/02 17:40:52.915] GET /psi_api/2003/?type=rules&uid=kn0m7BfWteec1ffd1f9e 117d33597247xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&
ui=agent&langroup=WORKGROUP&host=SYX01
[01/02 17:40:52.916] Request timeouts : 60000ms, 30000ms, 30000ms
[01/02 17:40:53.406] Error in HttpRequest: status=499, statusText='It was not possible to connect to the revocation serv
er or a definitive response could not be obtained.
',winCode=12057
[01/02 17:40:53.415] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:53.415] Error while fetching rules from server: "It was not possible to connect to the revocation server or
a definitive response could not be obtained.
"
[01/02 17:40:53.415] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:53.415] Unknown name in invoke:periodic
[01/02 17:40:53.415] Downloading software inspection rules from server
[01/02 17:40:53.415] An error occurred while downloading the rules (12057)
[01/02 17:40:53.415] Generating results
[01/02 17:40:53.415] Connecting to psi.secunia.com:443
[01/02 17:40:53.415] GET /psi_api/2003/?type=rules&uid=kn0m7BfWteec1ffd1f9e 117d33597247xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&
ui=agent&langroup=WORKGROUP&host=SYX01
[01/02 17:40:53.415] Request timeouts : 60000ms, 30000ms, 30000ms
[01/02 17:40:53.882] Error in HttpRequest: status=499, statusText='It was not possible to connect to the revocation serv
er or a definitive response could not be obtained.
',winCode=12057
[01/02 17:40:53.915] Error while fetching rules from server: "It was not possible to connect to the revocation server or
a definitive response could not be obtained.
"
[01/02 17:40:53.915] An error occurred while downloading the rules (12057)
[01/02 17:40:53.915] Generating results
[01/02 17:40:53.915] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:53.915] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:53.915] Unknown name in invoke:periodic
[01/02 17:40:54.165] Submitting results
[01/02 17:40:54.165] Connecting to psi.secunia.com:443
[01/02 17:40:54.166] POST /psi_api/2003/?type=data&scantype=1&tz=18000&domai n=0&uid=kn0m7BfWteec1ffd1f9e117d33597247xxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxx&ui=agent&langroup=WOR KGROUP&host=SYX01
[01/02 17:40:54.166] Request timeouts : 60000ms, 30000ms, 30000ms
[01/02 17:40:54.415] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:54.415] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:54.415] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:54.415]
#4000(CA)()
#4001(CF)(4)
#5019(F)()
! -> ##H12057:
#4003(A)()
#5017(S)()
#5020(A)()
[01/02 17:40:54.415] Unknown name in invoke:periodic
[01/02 17:40:54.633] Error in HttpRequest: status=499, statusText='It was not possible to connect to the revocation serv
er or a definitive response could not be obtained.
',winCode=12057
[01/02 17:40:54.665] Server returned 12057 : "It was not possible to connect to the revocation server or a definitive re
sponse could not be obtained.
"
[01/02 17:40:54.915] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:54.915] Unknown name in invoke:fUpdateScanStatus
[01/02 17:40:54.915]
#4000(CF)()
#4001(CF)(1)
#5019(F)()
! -> ##H12057:
#4003(CF)()
#5017(S)()
#5020(F)(1)
! -> ##H7505:, I12057
[01/02 17:40:54.915] Unknown name in invoke:periodic
[01/02 17:40:55.415] Unknown name in invoke:periodic
[01/02 17:40:55.915] Unknown name in invoke:periodic
[01/02 17:40:56.415] Unknown name in invoke:periodic
[01/02 17:40:56.915] Unknown name in invoke:periodic
Was this reply relevant?
+0
-0
E.Jeppesen RE: HELP Secunia cannot scan and psia log filled with errors
Secunia Official 4th Jan, 2013 13:48
Score: 220
Posts: 618
User Since: 24th Nov 2008
System Score: N/A
Location: Copenhagen, DK
Have you already followed the steps in this FAQ entry?
http://secunia.com/vulnerability_scanning/personal...
Were the "Secunia Update Agent" and "Secunia PSI Agent" set correctly?

mikeysrealm RE: HELP Secunia cannot scan and psia log filled with errors
Member 4th Jan, 2013 15:05
Score: 0
Posts: 5
User Since: 1st Jan 2013
System Score: N/A
Location: US
Thanks for the reply - I would really like to get PSI working - I have been using it since it was released, but I have been a bit frustrated by it of late.

I verified that active scripting was enabled for both internet and trusted sites and added https://*.secunia.com trusted sites to the list. No change in 2.0 behavior.

Note that once I add https://*.secunia.com/ to the trusted sites, then the Internet custom level doesn't apply to encrypted sites in the secunia.com domain, but the trusted sites custom level does - the FAQ should be updated to reflect this.
Was this reply relevant?
+0
-0
E.Jeppesen RE: HELP Secunia cannot scan and psia log filled with errors
Secunia Official 7th Jan, 2013 12:01
Score: 220
Posts: 618
User Since: 24th Nov 2008
System Score: N/A
Location: Copenhagen, DK
Just to be sure, were the "Secunia Update Agent" and "Secunia PSI Agent" set correctly?
mikeysrealm RE: HELP Secunia cannot scan and psia log filled with errors
Member 10th Jan, 2013 13:11
Score: 0
Posts: 5
User Since: 1st Jan 2013
System Score: N/A
Location: US
In the windows services console, there is only one secunia entry - "Secunia PSI Agent" - and it is set to automatic. There is no "Secunia Update Agent" listed.
Was this reply relevant?
+0
-0
E.Jeppesen RE: HELP Secunia cannot scan and psia log filled with errors
Secunia Official 11th Jan, 2013 09:29
Score: 220
Posts: 618
User Since: 24th Nov 2008
System Score: N/A
Location: Copenhagen, DK
Since you are missing the Secunia Update Agent you might want to try the solution in this thread.
http://secunia.com/community/forum/thread/show/136...

If that should not solve it then please see my comments in this thread.
http://secunia.com/community/forum/thread/show/132...
dennisx RE: HELP Secunia cannot scan and psia log filled with errors
Member 15th Jan, 2013 05:30
Score: 0
Posts: 2
User Since: 15th Jan 2013
System Score: N/A
Location: US
I started getting the same errors today (1-14-2013). PSI worked yesterday. I uninstalled and re installed, no joy. I uninstalled, deleted the registery key and re installed, no joy.

Why is it not working now?
Was this reply relevant?
+0
-0
Maurice Joyce RE: HELP Secunia cannot scan and psia log filled with errors
Handling Contributor 15th Jan, 2013 10:06
Score: 11792
Posts: 9,036
User Since: 4th Jan 2009
System Score: N/A
Location: UK
There was a major server outrage at Secunia that latest for many hours last night - is it working for you now?

--
Maurice

Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
16GB RAM
Was this reply relevant?
+0
-0
dennisx RE: HELP Secunia cannot scan and psia log filled with errors
Member 15th Jan, 2013 15:24
Score: 0
Posts: 2
User Since: 15th Jan 2013
System Score: N/A
Location: US
Yes, Thank you.
Was this reply relevant?
+0
-0

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer