Xerox 6180N FreeFlow® Print Server System Guide - Page 106

SNMP problems, Client problems, Windows problems

Page 106 highlights

Troubleshooting SNMP problems If there is no response from the agent to the browser, one or all of the following steps can be taken: 1. Log in as root. 2. # prstat This shows whether the agent is running or not. It may be that processes are consuming processor time. Normally you should see that the agent is taking up less than 1%. 3. ps -ef | grep agent This indicates if the agent is alive. The number 9252 is important for the pstack command below (the number varies). root 9252 9221 0 16:36:00 consoler 0:08 /opt/XRX/XRX/snmp/ agent 4. pstack 9252 You should see the above since the agent should be inactive most of the time. If you see something other than the above, the agent is not functioning properly. You may take an outload or call Service. Client problems Client problems are handled differently depending on the client platform used. Windows problems A job is submitted from a Windows client and is not received by the printer queue. If the Xerox Document Submission client application does not run properly or the job cannot be submitted to a queue, perform the following: The user must exit the Xerox Document Submission and Windows applications Verify the user is logged on to the appropriate file server. Restart the Xerox Document Submission software at the client workstation. 8-4 System Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136

8-4
System Guide
Troubleshooting
SNMP problems
If there is no response from the agent to the browser, one or all of
the following steps can be taken:
1.
Log in as root.
2.
# prstat
This shows whether the agent is running or not. It may be that
processes are consuming processor time. Normally you
should see that the agent is taking up less than 1%.
3.
ps -ef | grep agent
This indicates if the agent is alive. The number 9252 is
important for the pstack command below (the number varies).
root
9252
9221 0 16:36:00 consoler 0:08 /opt/XRX/XRX/snmp/
agent
4.
pstack
9252
You should see the above since the agent should be inactive
most of the time. If you see something other than the above,
the agent is not functioning properly. You may take an outload
or call Service.
Client problems
Client problems are handled differently depending on the client
platform used.
Windows problems
A job is submitted from a Windows client and is not received by
the printer queue.
If the Xerox Document Submission client application does not run
properly or the job cannot be submitted to a queue, perform the
following:
The user must exit the Xerox Document Submission and Windows
applications
Verify the user is logged on to the appropriate file server.
Restart the Xerox Document Submission software at the client
workstation.