08-06-2008
I've stopped and started lpsched, but the problem persists.
If I do a lpstat -p <printername> it does actually display the printer details. I'm also able to print to the printers.
Since the 16th of July the following message started appearing in /var/lp/logs/lpsched. I don't know if this has anything to do with the problem.
07/16 15:56:30: printer fault. type: write root, status: 14
msg: (exec exit fault)
07/16 15:57:31: printer fault. type: write root, status: 14
msg: (exec exit fault)
07/16 15:58:32: printer fault. type: write root, status: 14
msg: (exec exit fault)
07/16 15:59:33: printer fault. type: write root, status: 14
msg: (exec exit fault)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm in need of finding out on how to mount and dismount printers.
Thx,
shawnnee (1 Reply)
Discussion started by: shawnnee
1 Replies
2. UNIX for Dummies Questions & Answers
I just inst freeBSD boot installation and it didnt work for(probably my lack of knowledge) reasons but i now have to partitions in freeBSD and i really need them back for windows at the moment. i just cant find them. The bad thing is that i only got this bundled version of windows so i cant really... (2 Replies)
Discussion started by: riwa
2 Replies
3. UNIX for Dummies Questions & Answers
when i am doing the crontab editing i am using the setenv EDITOR /usr/bin/vi
but their was an error i tried to put set EDITOR /usr/bin/vi and it wnet through and i started editing using the command crontab -e but somehow it is slow and displayed something like e300 and i tried to stop because it... (3 Replies)
Discussion started by: afuella
3 Replies
4. UNIX Desktop Questions & Answers
I'm doing an assignment for a Unix course at school.
I attempted to rename one of the shell programming questions from home to Q1 by typing:
mv home Q1
It returned a message saying
mv: cannot access home
And now there's no home or Q1 in the directory. Please help! (8 Replies)
Discussion started by: slogged
8 Replies
5. Solaris
Hello all I was configuring a SUN 2540 raid and after a reboot the hba`s is gone.
There is no longer an entry in etc/path_to_inst for them (2 cards).
I tried a reconfigure boot several times but it does not work.
The hba`s is a SUN qlogic 2200 in x4240 server (AMD).
Using solaris 10 update7.... (6 Replies)
Discussion started by: vettec3
6 Replies
6. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
7. Solaris
Can't find the data in either pool.
bash-3.00# zoneadm -z PPSMzone1 move /zpool/ppsmzone1
cannot create ZFS dataset zpool/ppsmzone1: dataset already exists
Moving across file-systems; copying zonepath /rpool/PPSMzone1...
Cleaning up zonepath /rpool/PPSMzone1...
bash-3.00# zonecfg -z... (1 Reply)
Discussion started by: LittleLebowski
1 Replies
8. Post Here to Contact Site Administrators and Moderators
Dear admins,
it seems that some threads or even users have recently (~ 2 days or so) disappeared. Examples: giuliangiuseppe and greycells. The latter asked me for the solution I provided earlier this week.
What happened? Can you help?
Regards
Rüdiger (10 Replies)
Discussion started by: RudiC
10 Replies
9. Solaris
System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD.
I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies
10. Solaris
I have a problem where I installed several OSes as partitions on one disk. And suddenly I cannot see Solaris 11.3 in the bios boot screen anymore. I have no clue why. Do anyone have a suggestion so I can dig further somewhere?
I first installed Solaris 11.3. Then Windows10 (gaming). Then Linux... (3 Replies)
Discussion started by: kebabbert
3 Replies
fmd(1M) System Administration Commands fmd(1M)
NAME
fmd - fault manager daemon
SYNOPSIS
/usr/lib/fm/fmd/fmd [-V] [-f file] [-o opt=val] [-R dir]
DESCRIPTION
fmd is a daemon that runs in the background on each Solaris system. fmd receives telemetry information relating to problems detected by the
system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. When
appropriate, the fault manager also sends a message to the syslogd(1M) service to notify an administrator that a problem has been detected.
The message directs administrators to a knowledge article on Sun's web site, http://www.sun.com/msg/, which explains more about the problem
impact and appropriate responses.
Each problem diagnosed by the fault manager is assigned a Universal Unique Identifier (UUID). The UUID uniquely identifes this particular
problem across any set of systems. The fmdump(1M) utility can be used to view the list of problems diagnosed by the fault manager, along
with their UUIDs and knowledge article message identifiers. The fmadm(1M) utility can be used to view the resources on the system believed
to be faulty. The fmstat(1M) utility can be used to report statistics kept by the fault manager. The fault manager is started automatically
when Solaris boots, so it is not necessary to use the fmd command directly. Sun's web site explains more about what capabilities are cur-
rently available for the fault manager on Solaris.
OPTIONS
The following options are supported
-f file Read the specified configuration file prior to searching for any of the default fault manager configuration files.
-o opt=value Set the specified fault manager option to the specified value. Fault manager options are currently a Private inter-
face; see attributes(5) for information about Private interfaces.
-R dir Use the specified root directory for all pathnames evaluated by the fault manager, instead of the default root (/).
-V Print the fault manager's version to stdout and exit.
EXIT STATUS
The following exit values are returned:
0 Successful completion
1 An error occurred which prevented the fault manager from initializing, such as failure to open the telemetry trans-
port.
2 Invalid command-line options were specified.
FILES
/etc/fm/fmd Fault manager configuration directory
/usr/lib/fm/fmd Fault manager library directory
/var/fm/fmd Fault manager log directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWfmd |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), fmadm(1M), fmdump(1M), fmstat(1M), syslogd(1M), attributes(5), smf(5)
http://www.sun.com/msg/
NOTES
The Fault Manager is managed by the service management facility, smf(5), under the service identifier:
svc:/system/fmd:default
The service's status can be queried using the svcs(1) command. Administrators should not disable the Fault Manager service.
SunOS 5.10 17 Nov 2004 fmd(1M)