[INSTRM-827] Subaru archiver issue Created: 27/Nov/19  Updated: 03/Dec/19  Resolved: 28/Nov/19

Status: Done
Project: Instrument control development
Component/s: ics_archiver
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: arnaud.lefur Assignee: cloomis
Resolution: Done Votes: 0
Labels: SPS
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-187 Modify archiver's loadFile to allow u... Done
Story Points: 2
Sprint: SM1PD-2019 C

 Description   

archiver does not work properly 

2019-11-27 01:50:41-1000 [ReplyReceiver,client] 'database.loadFile failed for /software/mhs/logs/actors/archiver/archiver-557/reply_raw_17116 with error: OperationalError (see below for details)'                
2019-11-27 01:50:41-1000 [ReplyReceiver,client] 'could not open file "/software/mhs/logs/actors/archiver/archiver-557/reply_raw_17116" for reading: No such file or directory\nHINT:  COPY FROM instructs the Postg
reSQL server process to read a file. You may want a client-side facility such as psql\'s \\copy.\n'

2019-11-27 01:50:41-1000 [ReplyReceiver,client] 'database.loadFile failed for /software/mhs/logs/actors/archiver/archiver-557/reply_hdr_16613 with error: OperationalError (see below for details)'                
2019-11-27 01:50:41-1000 [ReplyReceiver,client] 'could not open file "/software/mhs/logs/actors/archiver/archiver-557/reply_hdr_16613" for reading: No such file or directory\nHINT:  COPY FROM instructs the Postg
reSQL server process to read a file. You may want a client-side facility such as psql\'s \\copy.\n'

Is that because postgresql is running on db-ics and archiver on mhs-ics ?

I cannot access db-ics, so I can't tell.



 Comments   
Comment by cloomis [ 28/Nov/19 ]

INSTRM-187 should have fixed exactly that. I'll look to see why that is not running or not working.

Comment by cloomis [ 28/Nov/19 ]

ics_archiver 1.2.2 was tested at JHU but I never installed it at Subaru. Installed and running.

Generated at Sat Feb 10 16:29:03 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.