Filter
Top Products
0030-0065 0030-0071
0030-0065 Could not open socket for debugger to communicate with poe.
Explanation: The socket() call failed when the debugger tried to set up communications
with POE.
User Response: Debugging can continue except that the information about synchronized
exit will not be passed back to the debugger from the POE job. Please note that the
debugger will most likely not be able to re-attach to this POE job after detaching.
0030-0066 Could not make socket connection to poe.
Explanation: The connect() call failed when the debugger tried to set up communications
with POE. The information about a synchronized exit is not passed back to the debugger
from the POE job.
User Response: You can continue debugging with limited function. Please note that the
debugger probably cannot re-attach to this POE job after detaching.
0030-0067 Could not read message from poe.
Explanation: pedb was unable to read data from the POE debug socket.
User Response: Debugging can continue except that the information about synchronized
exit may not be passed back to the debugger from the POE job. Please note that the
debugger will most likely not be able to re-attach to this POE job after detaching.
0030-0068 Could not write to poe debug socket.
Explanation: pedb was unable to write to the POE debug socket.
User Response: The debugger was unable to communicate to POE that the debugger is
detaching. Please note that the debugger will most likely not be able to re-attach to this
POE job.
0030-0069 An instance of pedb has already been attached to this poe job.
Explanation: Only one instance of the debugger may be attached to a given POE job at a
time. The existence of the /tmp/.pedb.<
poe-pid
>.host.list file indicates that pedb has already
attached to this POE job.
User Response: If pedb isn't currently attached to the POE job in question, remove the
corresponding .pedb.<
poe-pid
>.host.list file in /tmp, and try again.
0030-0070 Could not locate poe configuration file - '
string
'.
Explanation: pedb was unable to locate the POE configuration file.
User Response: Check to see if the desired POE job is running and if the configuration file
was created in /tmp. For example, check for a /tmp/.ppe.34192.attach.cfg file, where 34192
would be the process id of the POE job.)
0030-0071 The information in the poe configuration file has been modified and
therefore the old information is no longer valid. This is most likely due to a
poe job step ending.
Explanation: The POE configuration file,/tmp/.ppe.<
poe-pid
>.attach.cfg, was modified.
User Response: Restart the debugger in attach mode to debug the next POE job step.
Chapter 3. pedb Messages 29