Question
UBS
CH
Last activity: 13 Dec 2023 2:48 EST
file listener not starting after a system restart
Hi all
I've the following problem:
- file listener not starting after a system restart on the right node
- Manual restart works good
I've tried to follow the indication here:
QUESTION:
since I don't see any error in the log, is there a way to increase log level setting?
Accepted Solution
Updated: 13 Dec 2023 2:34 EST
Proximus
BE
Proximus
BE
Hello,
The file listener is supposed to be started for a specific Node Type.
It will be started for all nodes of this node type. Could you please clarify statement "not on the right node"
If you call a data page for some parameters, then it can be that it's not yet loaded, which is properly done when you do the start manually. Your requestor login should have the correct access group for this operation also.
Also check that block startup is not selected.
If you could clarify more on this file listener setup and issue, it would be easier to go through this issue
Regards
Anthony
UBS
CH
@Anthony_Gourtay Hallo Anthony
what I meant with "not on the right node" is the node defined -as node type- on the file listener itsself.
The listener simply doesn't start, however:
- Requestor has the permission (the listener can be started manually in the Admin Studio indeed)
- block startup is unchecked
is there a way to properly log/find some errors? What bother me, I can't see anything in the log
Accepted Solution
Updated: 13 Dec 2023 2:34 EST
Proximus
BE
Can you try by changing the node type ?
Maybe recheck & re-apply nodeType to avoid invisible char.
Please also hardcode any value in file listener if relevant for testing purpose.
Please confirm that the system AG is the same as your AG when you connect.
Since there's nothing printed in logs, it really looks like that the main condition for the nodetype is not fulfilled.
What you could also try is to put incorrect setup on purpose to trigger a failure.
- non existing directory to read, incorrect requestor login
Last, I think that DSS must be set to true
Pega-Engine • prconfig/initServices/initFile/default
Regards
Anthony
Proximus
BE
last: have you got other file listeners working? or it's one and this one only.
I once faced such issues and by re-creating it from an existing one, it finally worked.
We never found the reason, but since it was working....
So if you've got existing & working file listeners this is another approach you could try
Regards
Anthony
UBS
CH
@Anthony_Gourtay let me try this, I'll let you know, thanks
UBS
CH
@Anthony_Gourtay : the initFile dss works...thank you
Proximus
BE
@PieroGuido
Can you try by changing the node type ?
Maybe recheck & re-apply nodeType to avoid invisible char.
Please also hardcode any value in file listener if relevant for testing purpose.
Please confirm that the system AG is the same as your AG when you connect.
Since there's nothing printed in logs, it really looks like that the main condition for the nodetype is not fulfilled.
What you could also try is to put incorrect setup on purpose to trigger a failure.
- non existing directory to read, incorrect requestor login
Last, I think that DSS must be set to true
Pega-Engine • prconfig/initServices/initFile/default
Regards
Anthony