Professional Documents
Culture Documents
Case information
Product Version
Hostname
myrhbiogisdb01rhvp
Description
What problem/issue/behavior are you having trouble with? What do you expect to see?
We were performing Linux server reboot part of maintenance and upon completion of rebooting the server, we unable to
start the cups service.
Discussion
1 of 9
Raman, Muthu Sat, Feb 18, 2023, 08:31:23 AM GMT+8
Thanks a lot for the guidance and explanation to support on this case, and currently it is working fine and successful.
Regards,
Muthu Raman
Reply
2 of 9
Mason, Bryan Sat, Feb 18, 2023, 06:00:18 AM GMT+8
Hello Muthu,
Happy to hear that you were able to fix the problem! I’ll mark the case as closed. If you need further assistance on
this issue, please feel free to re-open it; and of course, don’t hesitate to open a new case if you have other issues
which we can help resolve. You may soon get a message to take part in an on-line survey; if you could fill it out,
that would be extremely helpful. The feedback helps us to continually improve our customer support.
~ Bryan
Reply
Hi Stephanie Leola,
Noted on this and as per your explanation and guidance notes yes due to the id "ms197943" which does not exist in the
server I was unable to start the CUPS service and currently have removed the id from the group in "/etc/cups/cups-
files.conf" file.
Currently able to start the service successfully without any error as per attached.
Thanks a lot for your support and guidance and currently CUPS working fine in the server, hence would close this case.
Regards,
Muthu Raman
Reply
SHA-256
9c40d8f5b9b6cc4b72797ca0949d00d32e6dc87295a7bae2402f73c3243cc3ae
Description
Delete
3 of 9
Leola Sousa, Stephanie Sat, Feb 18, 2023, 02:11:14 AM GMT+8
Hello,
The messages in the system journal explain why CUPS isn’t starting:
The group "ms197943", is missing from this system. I recommend either removing "ms197943" from the SystemGroup line in
/etc/cups/cups-files.conf or re-creating the "ms197943" group. This issue is described in the following Knowledgebase
Solution:
Reply
4 of 9
Raman, Muthu Sat, Feb 18, 2023, 01:58:19 AM GMT+8
Hi Stephanie Leola,
Thanks
Reply
5 of 9
Raman, Muthu Sat, Feb 18, 2023, 01:52:57 AM GMT+8
SHA-256
d28d04667ed28b11889edc1fbce035314b1e3db8e2bc5bcd8c2b5012804256bc
Description
sosreport file
Delete
Hi Bryan,
As per communicated, attached the sosreport requested on the server which having below issue.
Thanks
Regards,
Muthu Raman
Reply
6 of 9
Leola Sousa, Stephanie Sat, Feb 18, 2023, 01:38:19 AM GMT+8
Hello,
My name is stephanie and I’m working along with Bryan Mason in your case.
We gave you a call to acknowledge the case, thanks for your time during the call.
The sosreport was generated and soon as you get him uploaded we will be able to analyze it.
Reply
Hello,
So that we can begin to understand, diagnose, and resolve this issue, please provide a "sosreport" from the system
having difficulties. More information about sosreport and how to generate one can be found in the following
Knowledgebase Solution:
What is a sosreport and how to create one in Red Hat Enterprise Linux?
https://access.redhat.com/solutions/3592
~ Bryan
Reply
7 of 9
Mason, Bryan Sat, Feb 18, 2023, 12:58:02 AM GMT+8
Greetings,
My name is Bryan Mason; I’m a Software Engineer specializing in printing issues at Red Hat. I will begin to help
resolve this issue, although other Engineers may take ownership as appropriate. I may add updates that begin with
"//Internal Case Notes". Those updates contain information that I’m adding to the case for reference purposes as I
work to resolve the issue. They are there for your information and convenience, but do not require any action on your
part.
I’m currently reviewing all the data in the case in order to familiarize myself with this issue and your system
configuration. I will post further updates as I have information to share and findings to report.
Regards,
Bryan Mason
Principal Software Maintenance Engineer
Technical Support Delivery, North America
Reply
SHA-256
e266e04f09872826d196e953849cead8b141dff43c17fd6ff61e039e2bcef1e2
Description
Delete
Attached file =˛Error Details When Restarting CUPS Service Upon Server Reboot.jpg(343.1 kB
to
) this case.
SHA-256
257562970d6218d567582231b59ba7dc0d4ef3cb20e6338e8fcaa69d0a44b885
Description
Delete
Management
8 of 9
Owner *
A current phone number with the country code helps us support you better.
Group
RHEL
Alternate case ID
Send notifications
Enter an email address or username for the person you want to notify
24x7 Support
Action plan
No action plan to display.
Private Notes
Please note, contents of this field are not visible to Red Hat Support professionals.
9 of 9