Issues with installed printer and CUPS

Issues related to hardware problems
Post Reply
eyekay234
Posts: 7
Joined: 2021/03/15 17:38:05
Contact:

Issues with installed printer and CUPS

Post by eyekay234 » 2021/07/16 16:24:45

I have installed a HP Laser Jet 1018 printer on my centos 8 system. Anytime i plugin the usb cable to print and i check system services in administrative access mode using https://192.168.9.102:9090/system/services i keep seeing this error below:

configure-printer@usb-001-005 Configure Plugged-In Printer Failed to start

when i click on it, i get the following full message:

Configure Plugged-In Printer

Status
Static
Failed to start
Path
/usr/lib/systemd/system/configure-printer@.service

even when i click on start service it does nothing.

Further message i get is :

systemd
configure-printer@usb-001-005.service: Failed with result 'exit-code'.
CODE_FILE ../src/core/unit.c
CODE_FUNC unit_log_failure
CODE_LINE 5547
INVOCATION_ID 59752500c6d14bc88eb44de43da478aa
MESSAGE_ID d9b373ed55a64feb8242e02dbe79a49c
PRIORITY 4
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
UNIT configure-printer@usb-001-005.service
UNIT_RESULT exit-code
_BOOT_ID 30ae7b6c63424948a2824c89cba6c03d
_CAP_EFFECTIVE ffffffffff
_CMDLINE /usr/lib/systemd/systemd --switched-root --system --deserialize 17
_COMM systemd
_EXE /usr/lib/systemd/systemd
_GID 0
_HOSTNAME sotecorp
_MACHINE_ID 7c5f70c9eb864a169a33ed04e14af538
_PID 1
_SELINUX_CONTEXT system_u:system_r:init_t:s0
_SOURCE_REALTIME_TIMESTAMP 1626452370313088
_SYSTEMD_CGROUP /init.scope
_SYSTEMD_SLICE -.slice
_SYSTEMD_UNIT init.scope
_TRANSPORT journal
_UID 0
__CURSOR s=b4bca00818d645f98197a36badff201b;i=7f6;b=30ae7b6c63424948a2824c89cba6c03d;m=3411df5e;t=5c73ff3c6cf86;x=6dff66d62c1c2938
__MONOTONIC_TIMESTAMP 873586526
__REALTIME_TIMESTAMP 1626452370313094

How do i get this to work and print as it also doesnt allow me see the printer even after installing CUPS well

lightman47
Posts: 1521
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Issues with installed printer and CUPS

Post by lightman47 » 2021/07/17 15:19:39

Might those messages possibly be from machine boot-up when a driver poll for that device didn't find it connected and therefore couldn't start? (Don't know; just throwing that out there).

Post Reply