Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 
World Community Grid Forums
  Category: Completed Research
  Forum: Smash Childhood Cancer
  Thread: [Error] ATOM syntax incorrect: "62 " is not a valid atom number

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 101
Posts: 101   Pages: 11   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 20337 times and has 100 replies Next Thread
alanb1951
Veteran Cruncher
Joined: Jan 20, 2006
Post Count: 1317
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
Adri,
As I don't think that these posts belong here, I'd suggest to post sightings of these cases in a better fitting (new?) thread.
I'm inclined to agree, but where to put it? I've just been a wingman to an MCM1 task that had a 20 second deadline(!), and I haven't been through my databases looking for other examples yet but I'm sure there'll be more examples that are not for SCC1 :-)

Whilst there's a home for GPU stuff and a Hardware Chat forum, the only real application-independent homes for generic problems are News (where we can't create threads), the website forum (not really appropriate) and the client forum (definitely not appropriate in this case!)

If we park it in a thread here (with a note about only posting things about the topic at hand!) we could put similar threads in other forums (with examples for that project) to request that data be posted to said thread here (which may or may not work as planned!) What do you reckon???

And, regarding that thread you referenced, I wonder what Sekerob would have done here and now if it couldn't be turned into a FAQ and thus, hopefully, closed out :-)

Cheers - Al.

P.S. As a footnote to my previous comment in this thread, the MCM1 WU mentioned above sent out _0 and_1 (mine) at the same time, so nothing to do with prior client behaviour in this case...

[Quick edit to slightly re-word a couple of things...]
----------------------------------------
[Edit 1 times, last edit by alanb1951 at May 24, 2023 5:01:59 AM]
[May 24, 2023 4:53:51 AM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
Upon checking a few very recent workunits I noticed these ones, by chance situated between two MCM1-workunits:
workunit 312764210
MCM1_0199495_3829_0  MSWin 11      In Progress           2023-05-29T14:10:55  2023-06-04T14:10:55
MCM1_0199495_3829_1  MSWin 11      In Progress           2023-05-29T14:10:55  2023-06-04T14:10:55

workunit 312764209
SCC1_0004176_MyoD1-C_28332_0                Waiting to be sent

workunit 312764208
SCC1_0004176_MyoD1-C_28334_0                Waiting to be sent

workunit 312764207
SCC1_0004176_MyoD1-C_28335_0                Waiting to be sent

workunit 312764206
SCC1_0004176_MyoD1-C_28341_0                Waiting to be sent

workunit 312764205
MCM1_0199495_3827_0  Linux Ubuntu  In Progress           2023-05-29T14:10:59  2023-06-04T14:10:59
MCM1_0199495_3827_1  Linux Ubuntu  In Progress           2023-05-29T14:10:58  2023-06-04T14:10:58

These are SCC1-workunits from batch 0004176, one more than the erroneous batch at the start of this thread. I've seen workunits from that faulty batch 0004175 turning into state Other after the techs took action against them, so I wonder what will happen with this new batch. Maybe we will learn more later in the coming weeks …

Adri
[May 29, 2023 3:18:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
Just received the first few tasks from batch 0004176. Same error.

(Output generated by 'wcgstats -fSe* SCC1_0004176_MyoD1-C_0079')
workunit 311929205
SCC1_0004176_MyoD1-C_0079_0  Fedora Linux  Error  2023-06-01T21:19:10  2023-06-01T21:26:01    0.00/0.00
SCC1_0004176_MyoD1-C_0079_1  MSWin 10      InPrg  2023-06-01T21:26:20  2023-06-04T21:26:20    0.00/0.00
Details: ---------------------------------------------------------------------------------------------------------------------------------------
SCC1_0004176_MyoD1-C_0079_0  Fedora Linux  Error  2023-06-01T21:19:10  2023-06-01T21:26:01    0.00/0.00
	Logfile:
	<core_client_version>7.20.2</core_client_version>
	<message>
	process exited with code 1 (0x1, -255)</message>
	<stderr_txt>
	INFO: result number = 0
	INFO: No state to restore.  Start from the beginning.
	[23:22:31] Number of tasks = 1
	[23:22:31] Running task 0,CPU time at start of task 0 was 0.000000
	[23:22:31] ./cmpd-1100079.pdbqt size = 17 2 ../../projects/www.worldcommunitygrid.org/scc1.MyoD1-C.pdbqt size = 1268 0
	
	
	Parse error on line 190 in file "../../projects/www.worldcommunitygrid.org/25ab75759dee129fb753b48dcc421cf2.pdbqt": ATOM syntax incorrect: "62 " is not a valid atom number
	VINA failed.  rc = 1.  Exiting
	
	</stderr_txt>

(Output generated by 'wcgstats -fSe* SCC1_0004176_MyoD1-C_0091')
workunit 311929209
SCC1_0004176_MyoD1-C_0091_0  Fedora Linux  Error  2023-06-01T21:19:10  2023-06-01T21:26:01    0.00/0.00
SCC1_0004176_MyoD1-C_0091_1  Android       InPrg  2023-06-01T21:26:20  2023-06-04T21:26:20    0.00/0.00
SCC1_0004176_MyoD1-C_0091_2  Android       InPrg  2023-06-01T21:26:26  2023-06-04T21:26:26    0.00/0.00
Details: ---------------------------------------------------------------------------------------------------------------------------------------
SCC1_0004176_MyoD1-C_0091_0  Fedora Linux  Error  2023-06-01T21:19:10  2023-06-01T21:26:01    0.00/0.00
	Logfile:
	<core_client_version>7.20.2</core_client_version>
	<message>
	process exited with code 1 (0x1, -255)</message>
	<stderr_txt>
	INFO: result number = 0
	INFO: No state to restore.  Start from the beginning.
	[23:22:32] Number of tasks = 1
	[23:22:32] Running task 0,CPU time at start of task 0 was 0.000000
	[23:22:32] ./cmpd-1100091.pdbqt size = 16 3 ../../projects/www.worldcommunitygrid.org/scc1.MyoD1-C.pdbqt size = 1268 0
	
	
	Parse error on line 190 in file "../../projects/www.worldcommunitygrid.org/d7fcf338adbca38d9fbc24e0aa78fe3c.pdbqt": ATOM syntax incorrect: "62 " is not a valid atom number
	VINA failed.  rc = 1.  Exiting
	
	</stderr_txt>

The tasks start and crash immediately, just like all tasks in batch 0004175.

Adri
[Jun 1, 2023 9:35:43 PM]   Link   Report threatening or abusive post: please login first  Go to top 
AgrFan
Senior Cruncher
USA
Joined: Apr 17, 2008
Post Count: 396
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
Got 10 work units from batch 4176 today. 2 failed with the same error. I aborted the other 8 work units.

Most of today's work has been from batch 4158. Only getting batch 4176 work now. It's possible we're at the end of SCC work until this gets fixed.

It would be nice to hear why it takes so long to fix a syntax error. This should have been fixed 2 weeks ago ...
----------------------------------------

  • i5-10400 (Comet Lake, 6C/12T) @ 2.9 GHz
  • i5-7400 (Kaby Lake, 4C/4T) @ 3.0 GHz
  • i5-4590 (Haswell, 4C/4T) @ 3.3 GHz
  • i5-3330 (Ivy Bridge, 4C/4T) @ 3.0 GHz

----------------------------------------
[Edit 10 times, last edit by AgrFan at Jun 2, 2023 3:13:22 AM]
[Jun 2, 2023 12:26:42 AM]   Link   Report threatening or abusive post: please login first  Go to top 
bfmorse
Senior Cruncher
US
Joined: Jul 26, 2009
Post Count: 442
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
Just dIscovered the following SCC1 with errors (device/computer names have been replaced with "[REDACTED]"):

Results
Filter Panel Result name Device name Status Sent time Time due Return time Cpu time/ Elapsed time Claimed credit/ Granted credit

SCC1_0004176_MyoD1-C_2164_1 [REDACTED] Error 2023-06-02 04:26:18 UTC 2023-06-05 04:26:18 UTC 2023-06-02 04:34:42 UTC
SCC1_0004176_MyoD1-C_6516_0 [REDACTED] Error 2023-06-02 04:25:00 UTC 2023-06-08 04:25:00 UTC 2023-06-02 04:27:04 UTC
SCC1_0004176_MyoD1-C_6486_0 [REDACTED] Error 2023-06-02 04:22:57 UTC 2023-06-08 04:22:57 UTC 2023-06-02 04:25:00 UTC
SCC1_0004176_MyoD1-C_3973_2 [REDACTED] Error 2023-06-02 03:53:10 UTC 2023-06-05 03:53:10 UTC 2023-06-02 04:00:43 UTC
SCC1_0004176_MyoD1-C_6249_1 [REDACTED] Error 2023-06-02 03:49:15 UTC 2023-06-08 03:49:15 UTC 2023-06-02 03:51:18 UTC
SCC1_0004176_MyoD1-C_0439_2 [REDACTED] Error 2023-06-02 03:38:12 UTC 2023-06-05 03:38:12 UTC 2023-06-02 03:40:15 UTC
SCC1_0004176_MyoD1-C_6110_0 [REDACTED] Error 2023-06-02 03:28:25 UTC 2023-06-08 03:28:25 UTC 2023-06-02 03:31:04 UTC
SCC1_0004176_MyoD1-C_6100_0 [REDACTED] Error 2023-06-02 03:28:25 UTC 2023-06-08 03:28:25 UTC 2023-06-02 03:31:04 UTC
SCC1_0004176_MyoD1-C_6081_0 [REDACTED] Error 2023-06-02 03:26:22 UTC 2023-06-08 03:26:22 UTC 2023-06-02 03:28:25 UTC
SCC1_0004176_MyoD1-C_0000_2 [REDACTED] Error 2023-06-02 03:20:46 UTC 2023-06-05 03:20:46 UTC 2023-06-02 03:28:34 UTC
SCC1_0004176_MyoD1-C_5728_0 [REDACTED] Error 2023-06-02 02:11:25 UTC 2023-06-08 02:11:25 UTC 2023-06-02 02:13:32 UTC
SCC1_0004176_MyoD1-C_5662_1 [REDACTED] Error 2023-06-02 02:10:15 UTC 2023-06-08 02:10:15 UTC 2023-06-02 02:12:18 UTC
SCC1_0004176_MyoD1-C_5678_0 [REDACTED] Error 2023-06-02 02:10:10 UTC 2023-06-08 02:10:10 UTC 2023-06-02 02:12:17 UTC
SCC1_0004176_MyoD1-C_2219_3 [REDACTED] Error 2023-06-02 02:08:17 UTC 2023-06-05 02:08:17 UTC 2023-06-02 02:13:59 UTC
SCC1_0004176_MyoD1-C_5613_0 [REDACTED] Error 2023-06-02 02:07:13 UTC 2023-06-08 02:07:13 UTC 2023-06-02 02:10:10 UTC
SCC1_0004176_MyoD1-C_5442_0 [REDACTED] Error 2023-06-02 01:53:23 UTC 2023-06-08 01:53:23 UTC 2023-06-02 01:57:13 UTC
SCC1_0004176_MyoD1-C_5387_0 [REDACTED] Error 2023-06-02 01:51:20 UTC 2023-06-08 01:51:20 UTC 2023-06-02 01:57:13 UTC
SCC1_0004176_MyoD1-C_5241_0 [REDACTED] Error 2023-06-02 01:42:14 UTC 2023-06-08 01:42:14 UTC 2023-06-02 01:44:38 UTC
SCC1_0004176_MyoD1-C_5245_0 [REDACTED] Error 2023-06-02 01:42:14 UTC 2023-06-08 01:42:14 UTC 2023-06-02 01:44:38 UTC
SCC1_0004176_MyoD1-C_0936_2 [REDACTED] Error 2023-06-02 01:38:08 UTC 2023-06-05 01:38:08 UTC 2023-06-02 01:40:11 UTC
SCC1_0004176_MyoD1-C_2192_1 [REDACTED] Error 2023-06-02 01:31:17 UTC 2023-06-05 01:31:17 UTC 2023-06-02 01:39:12 UTC
SCC1_0004176_MyoD1-C_5126_0 [REDACTED] Error 2023-06-02 01:25:58 UTC 2023-06-08 01:25:58 UTC 2023-06-02 01:29:58 UTC
SCC1_0004176_MyoD1-C_5127_0 [REDACTED] Error 2023-06-02 01:25:58 UTC 2023-06-08 01:25:58 UTC 2023-06-02 01:29:58 UTC
SCC1_0004176_MyoD1-C_4820_1 [REDACTED] Error 2023-06-02 01:05:13 UTC 2023-06-08 01:05:13 UTC 2023-06-02 01:13:26 UTC
SCC1_0004176_MyoD1-C_4683_0 [REDACTED] Error 2023-06-02 0:53:44 UTC 2023-06-08 0:53:44 UTC 2023-06-02 03:33:54 UTC
SCC1_0004176_MyoD1-C_4677_0 [REDACTED] Error 2023-06-02 0:52:22 UTC 2023-06-08 0:52:22 UTC 2023-06-02 0:54:25 UTC
SCC1_0004176_MyoD1-C_4635_2 [REDACTED] Error 2023-06-02 0:51:41 UTC 2023-06-05 0:51:41 UTC 2023-06-02 0:57:48 UTC
SCC1_0004176_MyoD1-C_3205_1 [REDACTED] Error 2023-06-02 0:45:59 UTC 2023-06-05 0:45:59 UTC 2023-06-02 0:54:42 UTC
SCC1_0004176_MyoD1-C_4384_0 [REDACTED] Error 2023-06-02 0:33:07 UTC 2023-06-08 0:33:07 UTC 2023-06-02 0:35:10 UTC
SCC1_0004176_MyoD1-C_0920_4 [REDACTED] Error 2023-06-02 0:31:42 UTC 2023-06-05 0:31:42 UTC 2023-06-02 0:39:30 UTC
SCC1_0004176_MyoD1-C_4336_0 [REDACTED] Error 2023-06-02 0:30:14 UTC 2023-06-08 0:30:14 UTC 2023-06-02 0:32:17 UTC
SCC1_0004176_MyoD1-C_4202_1 [REDACTED] Error 2023-06-02 0:22:52 UTC 2023-06-08 0:22:52 UTC 2023-06-02 0:37:02 UTC
SCC1_0004176_MyoD1-C_4216_0 [REDACTED] Error 2023-06-02 0:22:40 UTC 2023-06-08 0:22:40 UTC 2023-06-02 0:24:43 UTC
SCC1_0004176_MyoD1-C_3990_0 [REDACTED] Error 2023-06-01 23:53:42 UTC 2023-06-07 23:53:42 UTC 2023-06-01 23:55:45 UTC
SCC1_0004176_MyoD1-C_0254_1 [REDACTED] Error 2023-06-01 23:40:46 UTC 2023-06-04 23:40:46 UTC 2023-06-01 23:48:22 UTC
SCC1_0004176_MyoD1-C_3787_0 [REDACTED] Error 2023-06-01 23:40:07 UTC 2023-06-07 23:40:07 UTC 2023-06-01 23:43:20 UTC
SCC1_0004176_MyoD1-C_3742_0 [REDACTED] Error 2023-06-01 23:35:10 UTC 2023-06-07 23:35:10 UTC 2023-06-01 23:37:44 UTC
SCC1_0004176_MyoD1-C_3744_0 [REDACTED] Error 2023-06-01 23:35:10 UTC 2023-06-07 23:35:10 UTC 2023-06-01 23:37:44 UTC
SCC1_0004176_MyoD1-C_3526_2 [REDACTED] Error 2023-06-01 23:22:47 UTC 2023-06-04 23:22:47 UTC 2023-06-01 23:24:54 UTC
SCC1_0004176_MyoD1-C_0520_4 [REDACTED] Error 2023-06-01 23:17:15 UTC 2023-06-04 23:17:15 UTC 2023-06-01 23:22:37 UTC
SCC1_0004176_MyoD1-C_0159_4 [REDACTED] Error 2023-06-01 22:57:59 UTC 2023-06-04 22:57:59 UTC 2023-06-01 23:00:03 UTC 84.5 / 0
SCC1_0004176_MyoD1-C_3201_0 [REDACTED] Error 2023-06-01 22:47:46 UTC 2023-06-07 22:47:46 UTC 2023-06-01 22:49:49 UTC
SCC1_0004176_MyoD1-C_3117_3 [REDACTED] Error 2023-06-01 22:46:32 UTC 2023-06-04 22:46:32 UTC 2023-06-01 22:48:39 UTC
SCC1_0004176_MyoD1-C_3170_0 [REDACTED] Error 2023-06-01 22:45:57 UTC 2023-06-07 22:45:57 UTC 2023-06-01 22:48:00 UTC
SCC1_0004176_MyoD1-C_0855_1 [REDACTED] Error 2023-06-01 22:38:53 UTC 2023-06-04 22:38:53 UTC 2023-06-01 22:46:31 UTC
SCC1_0004176_MyoD1-C_3029_0 [REDACTED] Error 2023-06-01 22:32:44 UTC 2023-06-07 22:32:44 UTC 2023-06-01 22:35:33 UTC
SCC1_0004176_MyoD1-C_3027_0 [REDACTED] Error 2023-06-01 22:32:44 UTC 2023-06-07 22:32:44 UTC 2023-06-01 22:35:33 UTC
SCC1_0004176_MyoD1-C_2904_0 [REDACTED] Error 2023-06-01 22:28:38 UTC 2023-06-07 22:28:38 UTC 2023-06-01 22:30:41 UTC
SCC1_0004176_MyoD1-C_2707_0 [REDACTED] Error 2023-06-01 22:26:09 UTC 2023-06-07 22:26:09 UTC 2023-06-01 22:28:38 UTC
SCC1_0004176_MyoD1-C_2699_0 [REDACTED] Error 2023-06-01 22:26:09 UTC 2023-06-07 22:26:09 UTC 2023-06-01 22:28:38 UTC
SCC1_0004176_MyoD1-C_2601_0 [REDACTED] Error 2023-06-01 22:24:06 UTC 2023-06-07 22:24:06 UTC 2023-06-01 22:26:09 UTC
SCC1_0004176_MyoD1-C_2468_1 [REDACTED] Error 2023-06-01 22:23:55 UTC 2023-06-04 22:23:55 UTC 2023-06-01 22:25:58 UTC
SCC1_0004176_MyoD1-C_2358_2 [REDACTED] Error 2023-06-01 22:20:35 UTC 2023-06-04 22:20:35 UTC 2023-06-01 22:22:53 UTC
SCC1_0004176_MyoD1-C_2378_1 [REDACTED] Error 2023-06-01 22:13:18 UTC 2023-06-07 22:13:18 UTC 2023-06-01 22:20:40 UTC
SCC1_0004176_MyoD1-C_2371_0 [REDACTED] Error 2023-06-01 22:13:13 UTC 2023-06-07 22:13:13 UTC 2023-06-01 22:15:17 UTC
SCC1_0004176_MyoD1-C_2304_1 [REDACTED] Error 2023-06-01 22:10:02 UTC 2023-06-07 22:10:02 UTC 2023-06-01 22:12:06 UTC
SCC1_0004176_MyoD1-C_2190_0 [REDACTED] Error 2023-06-01 22:07:26 UTC 2023-06-07 22:07:26 UTC 2023-06-01 22:10:51 UTC
SCC1_0004176_MyoD1-C_1829_0 [REDACTED] Error 2023-06-01 21:58:51 UTC 2023-06-07 21:58:51 UTC 2023-06-01 22:00:59 UTC
SCC1_0004176_MyoD1-C_1735_0 [REDACTED] Error 2023-06-01 21:57:28 UTC 2023-06-07 21:57:28 UTC 2023-06-02 03:16:40 UTC
SCC1_0004176_MyoD1-C_1664_0 [REDACTED] Error 2023-06-01 21:56:48 UTC 2023-06-07 21:56:48 UTC 2023-06-01 21:58:51 UTC
SCC1_0004176_MyoD1-C_1429_0 [REDACTED] Error 2023-06-01 21:47:59 UTC 2023-06-07 21:47:59 UTC 2023-06-01 21:51:43 UTC
SCC1_0004176_MyoD1-C_1131_0 [REDACTED] Error 2023-06-01 21:41:11 UTC 2023-06-07 21:41:11 UTC 2023-06-01 21:47:08 UTC
SCC1_0004176_MyoD1-C_1054_1 [REDACTED] Error 2023-06-01 21:39:03 UTC 2023-06-07 21:39:03 UTC 2023-06-01 21:46:07 UTC
SCC1_0004176_MyoD1-C_0822_0 [REDACTED] Error 2023-06-01 21:32:29 UTC 2023-06-07 21:32:29 UTC 2023-06-01 21:41:11 UTC
SCC1_0004176_MyoD1-C_0535_0 [REDACTED] Error 2023-06-01 21:25:50 UTC 2023-06-07 21:25:50 UTC 2023-06-01 21:33:49 UTC
SCC1_0004176_MyoD1-C_0543_0 [REDACTED] Error 2023-06-01 21:25:31 UTC 2023-06-07 21:25:31 UTC 2023-06-01 21:33:34 UTC
SCC1_0004176_MyoD1-C_0232_1 [REDACTED] Error 2023-06-01 21:20:24 UTC 2023-06-07 21:20:24 UTC 2023-06-01

Results log [from a representative WU]

<core_client_version>7.20.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
INFO: result number = 0
INFO: No state to restore. Start from the beginning.
[18:26:16] Number of tasks = 1
[18:26:16] Running task 0,CPU time at start of task 0 was 0.000000
[18:26:16] ./cmpd-1102699.pdbqt size = 17 4 ../../projects/www.worldcommunitygrid.org/scc1.MyoD1-C.pdbqt size = 1268 0


Parse error on line 190 in file "..\..\projects\www.worldcommunitygrid.org\0c043e7078c21f5384341ccd5bb217f8.pdbqt": ATOM syntax incorrect: "62 " is not a valid atom number
VINA failed. rc = 1. Exiting

</stderr_txt>
]]>
[Jun 2, 2023 4:59:53 AM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
First I verified that my "reliable" state had been reinstated (because, after running two error tasks my device lost its reliability status temporarily) - I did this by checking if I was getting any singletons validated in the past few hours, and I did indeed get them:
$ wcgstats -ws1 -aSCC1 -m9 -sC -t3 -rrrS
* Showing page 1/84 of all SCC1-tasks with status ’C’ on device 9 (ID=8403220) (”[redacted]”):
 <1> * SCC1_0004158_MyoD1-B_69076_0  Fedora Linux  Valid  2023-06-01T15:04:37  2023-06-02T08:50:28    0.85/0.86

 <2> * SCC1_0004158_MyoD1-B_68867_0  Fedora Linux  Valid  2023-06-01T15:02:29  2023-06-02T08:50:28    0.94/0.94

 <3> * SCC1_0004158_MyoD1-B_67872_0  Fedora Linux  Valid  2023-06-01T14:49:34  2023-06-02T08:48:20    1.13/1.14

 <4>   SCC1_0004085_MyoD1-A_28691_0  Linux Debian  Valid  2023-05-28T15:41:06  2023-06-02T07:11:52  107.70/109.92
 <4> * SCC1_0004085_MyoD1-A_28691_1  Fedora Linux  Valid  2023-06-02T07:32:17  2023-06-02T08:41:59    1.14/1.15

 <5> * SCC1_0004158_MyoD1-B_67869_0  Fedora Linux  Valid  2023-06-01T14:49:34  2023-06-02T08:39:52    0.97/0.98

 <6> * SCC1_0004158_MyoD1-B_67715_0  Fedora Linux  Valid  2023-06-01T14:47:26  2023-06-02T08:39:52    1.00/1.01

 <7> * SCC1_0004158_MyoD1-B_65340_0  Fedora Linux  Valid  2023-06-01T14:23:58  2023-06-02T08:37:45    1.23/1.24

 <8> * SCC1_0004158_MyoD1-B_66421_0  Fedora Linux  Valid  2023-06-01T14:34:41  2023-06-02T08:37:45    1.17/1.18

 <9> * SCC1_0004158_MyoD1-B_67164_0  Fedora Linux  Valid  2023-06-01T14:41:04  2023-06-02T08:35:37    1.11/1.12

<10> * SCC1_0004158_MyoD1-B_67873_0  Fedora Linux  Valid  2023-06-01T14:49:34  2023-06-02T08:35:37    0.85/0.85

Then I verified if there were any tasks from batch 0004176 (type scc1.MyoD1-C) on my device that didn't need verification:

$ wcgstats -ws1 -aSCC1 -m9 -Sr -p8
* Let's try to locate the workunit.
There are 19 pages of results available.

* Showing page 8/19 of all SCC1-tasks with status ’1’ on device 9 (ID=8403220) (”[redacted]”):

[... skipping some entries ...]

<11>   SCC1_0004176_MyoD1-C_0536_0  Linux Ubuntu  Error      2023-06-01T21:25:49  2023-06-01T21:27:57    0.00/0.00
<11> * SCC1_0004176_MyoD1-C_0536_1  Fedora Linux  In Progr.  2023-06-01T21:26:01  2023-06-07T21:26:01    0.00/0.00
<11>   SCC1_0004176_MyoD1-C_0536_2  Linux Ubuntu  Error      2023-06-01T21:28:05  2023-06-01T22:10:24    0.00/0.00
<11>   SCC1_0004176_MyoD1-C_0536_3  Linux Ubuntu  Error      2023-06-01T22:10:40  2023-06-02T01:09:44    0.00/0.00
<11>   SCC1_0004176_MyoD1-C_0536_4  Linuxmint     In Progr.  2023-06-02T01:10:12  2023-06-05T01:10:12    0.00/0.00

<12> * SCC1_0004176_MyoD1-C_0308_0  Fedora Linux  In Progr.  2023-06-01T21:21:18  2023-06-07T21:21:18    0.00/0.00

<13> * SCC1_0004176_MyoD1-C_0299_0  Fedora Linux  In Progr.  2023-06-01T21:21:18  2023-06-07T21:21:18    0.00/0.00

So I found these two above: _0308_0 and _0299_0. These two didn't have a 'partner' yet and my device should be reliable now.
This was the moment to fix the error in the configuration files:

# cd ~boinc/projects/www.worldcommunitygrid.org
# a=$(grep -l ^ATOM"    62 " [0-9a-f]*.pdbqt 2>/dev/null)
# [ -n "$a" ] && printf "HOT FIX for:\n%s\n" "$a" && sed -i 's/^ATOM    62 /ATOM     62 /' $a && ls -l $a
HOT FIX for:
3b8dd18abe4029e613926298556832c6.pdbqt
65b51ee6a9ad6f119f9c06cd40923361.pdbqt
-rw-r--r--. 1 boinc boinc 9298 Jun  1 23:40 3b8dd18abe4029e613926298556832c6.pdbqt
-rw-r--r--. 1 boinc boinc 9298 Jun  1 23:40 65b51ee6a9ad6f119f9c06cd40923361.pdbqt

Then it was time to run the two tasks, temporarily suspending a number of other tasks to let the two get started. They started running. In the meantime, I suspended all the other MyoD1-C-type tasks, so that no other C-type tasks would be downloaded and disturb the process. After about one hour they both finished, a few minutes apart from each other. The suspended tasks were resumed by me after confirming that both C-type tasks were uploaded and reported. Then I checked the completed tasks again:
$ wcgstats -ws1 -aSCC1 -m9 -sC -t3 -rrrS
* Let's try to locate the workunit.
There are 84 pages of results available.

* Showing page 1/84 of all SCC1-tasks with status ’C’ on device 9 (ID=8403220) (”[redacted]”):
 <1> * SCC1_0004176_MyoD1-C_0299_0  Fedora Linux  Valid  2023-06-01T21:21:18  2023-06-02T09:46:32    0.77/0.78

 <2> * SCC1_0004158_MyoD1-B_71142_0  Fedora Linux  P.Ver  2023-06-01T15:32:15  2023-06-02T09:42:14    1.10/1.11
 <2>   SCC1_0004158_MyoD1-B_71142_1                Wait.                                              0.00/0.00

 <3> * SCC1_0004176_MyoD1-C_0308_0  Fedora Linux  P.Ver  2023-06-01T21:21:18  2023-06-02T09:42:14    0.73/0.73
 <3>   SCC1_0004176_MyoD1-C_0308_1                Wait.                                              0.00/0.00

Yes! dancing One C-type task is Valid. good luck

Unfortunately, the other one needs verification and I'm afraid no-one will notice they have a chance to get a Valid C-type task by following the procedure to fix the error (see above, a=... etc.).

Adri
PS So, if you are the lucky one to catch this one:
(Output generated by 'wcgstats -fS* SCC1_0004176_MyoD1-C_0308')
workunit 311931322
SCC1_0004176_MyoD1-C_0308_0  Fedora Linux  Pending Verification  2023-06-01T21:21:18  2023-06-02T09:42:14
SCC1_0004176_MyoD1-C_0308_1                Waiting to be sent

[Jun 2, 2023 10:20:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Mike.Gibson
Ace Cruncher
England
Joined: Aug 23, 2007
Post Count: 12594
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
The only SCC I am getting are 4176 with ATOM 62 errors.

Mike
[Jun 2, 2023 12:06:01 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7846
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
I have 42 SCC 4176 errors no valid or pending. Probably because of these errors, I have 95 pending verification which is an unusually high number. Batches 4175 and 4176 seem to be history as the following batches 4152, 4157, 4158, 4159, 4085, and 4089 are all validating.
Cheers
Edit: I spoke too soon. They still seem to be issuing the 4176 batch. I started it and it immediately had an error. You would have thought they would have pulled all of them by now.
Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
----------------------------------------
[Edit 1 times, last edit by Sgt.Joe at Jun 2, 2023 4:02:30 PM]
[Jun 2, 2023 12:53:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
sptrog1
Master Cruncher
Joined: Dec 12, 2017
Post Count: 1592
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
I have received 3 of the batch 4176 with errors do I just ignore them.
[Jun 2, 2023 2:15:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
TPCBF
Master Cruncher
USA
Joined: Jan 2, 2011
Post Count: 2173
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: [Error] ATOM syntax incorrect: "62 " is not a valid atom number
It just never ends!

Then then they wonder why people get upset! devilish

Yet another fouled up batch, this time 4176

SCC1_0004176_MyoD1-C_5830

Immediately bombs out with computation error.

And yet again, just crickets from WCG tower... sad


Ralf
[Jun 2, 2023 2:33:36 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 101   Pages: 11   [ Previous Page | 1 2 3 4 5 6 7 8 9 10 | Next Page ]
[ Jump to Last Post ]
Post new Thread