BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
sathya66
Barite | Level 11

All,

I am getting below message on linux box screen when we restart lsf and pm services

Broadcast message from systemd-journald@sashost (Thu 2023-03-16 15:01:08 GMT):

mbatchd[25903]: You must make LSF_LIVE_CONFDIR accessible and run badmin mbdrestart or badmin reconfig to use bconf.


Message from syslogd@10.20.105.80 at Mar 16 15:01:08 ...
 mbatchd[25903]:You must make LSF_LIVE_CONFDIR accessible and run badmin mbdrestart or badmin reconfig to use bconf.

Broadcast message from systemd-journald@sashost (Thu 2023-03-16 15:01:08 GMT):

mbatchd[25903]: You must make LSF_LIVE_CONFDIR accessible and run badmin mbdrestart or badmin reconfig to use bconf.


Message from syslogd@10.20.105.80 at Mar 16 15:01:08 ...
 mbatchd[25903]:You must make LSF_LIVE_CONFDIR accessible and run badmin mbdrestart or badmin reconfig to use bconf.

when I try to to badmin, I am getting LSF is down message and nothing happening

badmin reconfig
Checking configuration files ...

No errors found.

LSF is down. Please wait ...
LSF is down. Please wait ...
LSF is down. Please wait ...
LSF is down. Please wait ...

and when I see the res log

 Mar 16 15:02:10 2023 23281 3 10.1 verifyEAuth/lib.eauth.c: b_read_fix <0 0 root 10.20.105.80 0 16 user res /tmp/.auxrdNP9TJ NULL
> failed, cc=0: Connection reset by peer
Mar 16 15:02:10 2023 23281 3 10.1 userok: eauth authentication failed for root/10.20.105.80
Mar 16 15:02:10 2023 23281 3 10.1 doacceptconn: Permission denied root(0)@sashost

lim.log

 Mar 16 14:56:04 2023 23277 4 3.4.0 initNewMaster: This is now the master host.
Mar 16 14:56:04 2023 23277 4 3.4.0 System daemon VEMKD is down on host <sashost> in cluster <cluster>

mbatchd.log

Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.users) failed.
Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.hosts) failed.
Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.queues) failed.
Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.resources) failed.
Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.applications) failed.
Mar 16 14:56:04 2023 23479:23479 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.serviceclasses) failed.
Mar 16 14:57:38 2023 24229:24229 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.serviceclasses) failed.
Mar 16 14:59:08 2023 24897:24897 3 10.1 LiC_CreateAConfControlSum(): stat(/lsf/conf/lsbatch/cluster/configdir/lsb.serviceclasses) failed.

when I try to stop the lsf services , I am getting below error

Shut down RES on <sashost> ...... ls_rescontrol: User permission denied

what is causing this issue.
thanks in advance .

 

1 ACCEPTED SOLUTION

Accepted Solutions
sathya66
Barite | Level 11

This issue is resolved. It is to do with permissions on lsf_confdir folder . Someone has changed the permissions to 700 and lsf services are not running.Put it to 755 and worked.

View solution in original post

1 REPLY 1
sathya66
Barite | Level 11

This issue is resolved. It is to do with permissions on lsf_confdir folder . Someone has changed the permissions to 700 and lsf services are not running.Put it to 755 and worked.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 1147 views
  • 0 likes
  • 1 in conversation