Advertisements

Category Archives: Linux

Starting INET services. (xinetd) failed

xinetd is not starting

root@linux:~ # service xinetd start
Starting INET services. (xinetd) failed

No services managed by xinetd are available

root@linux:~ # tail -20 /var/log/messages
Oct 9 06:15:04 linux run-crons[14711]: eds-ntpdate: OK
Oct 9 06:39:45 linux — MARK —
Oct 9 06:59:45 linux — MARK —
Oct 9 07:15:04 linux run-crons[31922]: eds-ntpdate: OK
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.conf] [line=26]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/chargen-udp [file=/etc/xinetd.d/chargen-udp] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=15]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/daytime-udp [file=/etc/xinetd.d/daytime-udp] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard] [line=15]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/discard-udp [file=/etc/xinetd.d/discard-udp] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=15]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/echo-udp [file=/etc/xinetd.d/echo-udp] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/netstat [file=/etc/xinetd.d/netstat] [line=15]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/rsync [file=/etc/xinetd.d/rsync] [line=16]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/servers [file=/etc/xinetd.d/servers] [line=12]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/services [file=/etc/xinetd.d/services] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/systat [file=/etc/xinetd.d/systat] [line=14]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=17]
Oct 9 07:30:51 linux xinetd[15114]: Reading included configuration file: /etc/xinetd.d/time-udp [file=/etc/xinetd.d/time-udp] [line=15]
Oct 9 07:30:51 linux xinetd[15114]: 15114 {init_services} no services. Exiting…

Enabling sysstat changing disable = yes to disable = no

root@linux:~ # vi /etc/xinetd.d/sysstat
# Finger, systat and netstat give out user information which may be
# valuable to potential “system crackers.” Many sites choose to disable
# some or all of these services to improve security.
# Try “telnet localhost systat” and “telnet localhost netstat” to see that
# information yourself!
#
service systat
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = nobody
server = /bin/ps
server_args = -auwwx
}

Starting service xinetd

root@linux:~ # service xinetd start
Starting INET services. (xinetd) done

Advertisements

Connect Enterprise error: A0x0401: Login failed

ceuser@linux:~ $ cmulist -Q -t 16
A0x0401: Login failed
Make sure that CMUPORT, CMUHOST and other connection information are properly set

I’m receiving this error but didn’t find a solution yet

Using telnet and it was pointing to a wrong address. Ping was directing to correct IP address

linux was solving hostname to an incorrect IP address when using telnet

root@linux:~ # telnet host24100
Trying 172.22.12.135…
telnet: connect to address 172.22.12.135: Connection refused

It was solving to the correct IP address when using ping

root@linux:~ # ping -c1 host24100
PING host099.setaoffice.com (172.22.84.143) 56(84) bytes of data.
64 bytes from host27100.setaoffice.com (172.22.84.143): icmp_seq=1 ttl=127 time=1.32 ms

— host099.setaoffice.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.321/1.321/1.321/0.000 ms

I’ve restarted nscd service

root@linux:~ # service nscd status
Checking for Name Service Cache Daemon: running

root@linux:~ # service nscd stop
Shutting down Name Service Cache Daemon done

root@linux:~ # service nscd start
Starting Name Service Cache Daemon done

After the restart, it started to point to the correct IP address

root@linux:~ # telnet host24100 24100
Trying 172.22.84.143…
Connected to host24100.
Escape character is ‘^]’.
0G^]
telnet> quit
Connection closed.

Booting Linux into single user or emergency mode

For Red Hat Enterprise Linux 6
Single-User Mode
Single-user mode provides a Linux environment for a single user that allows you to recover your system from problems that cannot be resolved in networked multi-user environment. You do not need an external boot device to be able to boot into single-user mode, and you can switch into it directly while the system is running.

At the GRUB boot screen, press any key to enter the GRUB interactive menu.
Select Red Hat Enterprise Linux with the version of the kernel that you want to boot and press the a to append the line.
Type single as a separate word at the end of the line and press Enter to exit GRUB edit mode. Alternatively, you can type 1 instead of single.

Emergency Mode
Emergency mode, provides the minimal bootable environment and allows you to repair your system even in situations when rescue mode is unavailable. In emergency mode, the system mounts only the root file system, and it is mounted as read-only. Also, the system does not activate any network interfaces and only a minimum of the essential services are set up. The system does not load any init scripts, therefore you can still mount file systems to recover data that would be lost during a re-installation if init is corrupted or not working.

At the GRUB boot screen, press any key to enter the GRUB interactive menu.
Select Red Hat Enterprise Linux with the version of the kernel that you want to boot and press the a to append the line.
Type emergency as a separate word at the end of the line and press Enter to exit GRUB edit mode.

smbclient receiving error message: protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

I have a Red Hat Enterprise Linux 7.5 server that is not connecting to a Windows share

root@linux:~ # cat /etc/*release
NAME=”Red Hat Enterprise Linux Server”
VERSION=”7.5 (Maipo)”
ID=”rhel”
ID_LIKE=”fedora”
VARIANT=”Server”
VARIANT_ID=”server”
VERSION_ID=”7.5″
PRETTY_NAME=”Red Hat Enterprise Linux”
ANSI_COLOR=”0;31″
CPE_NAME=”cpe:/o:redhat:enterprise_linux:7.5:GA:server”
HOME_URL=”https://www.redhat.com/”
BUG_REPORT_URL=”https://bugzilla.redhat.com/”

REDHAT_BUGZILLA_PRODUCT=”Red Hat Enterprise Linux 7″
REDHAT_BUGZILLA_PRODUCT_VERSION=7.5
REDHAT_SUPPORT_PRODUCT=”Red Hat Enterprise Linux”
REDHAT_SUPPORT_PRODUCT_VERSION=”7.5″
Red Hat Enterprise Linux Server release 7.5 (Maipo)
Red Hat Enterprise Linux Server release 7.5 (Maipo)

samba rebased to version 4.6.2

To improve security, the NT LAN manager version 1 (NTLMv1) protocol is now disabled by default. If you require the insecure NTLMv1 protocol, set the ntlm auth parameter in the /etc/samba/smb.conf file to yes.

The storage was upgraded so my RHEL 7.5 server is the client trying to connect to the Windows share. It is showing the message protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

root@linux:~ # smbclient //storageserver/PUBLICO -U “setaoffice/username%PASSWORD” -c ‘prompt; cd CC_EFC_Inbound/Logs; mget *.log’
protocol negotiation failed: NT_STATUS_CONNECTION_DISCONNECTED

To solve the problem, I had to add -m SMB2 or -m SMB3 to the smbclient

root@linux:~ # smbclient //storageserver/PUBLICO -U “setaoffice/username%PASSWORD” -m SMB2 -c ‘prompt; cd CC_EFC_Inbound/Logs; mget *.log’
Kinit for username@SETAOFFICE to access storageserver failed: Cannot find KDC for requested realm
session setup failed: NT_STATUS_WRONG_PASSWORD

Control-M: The SMTP server did not respond in a timely manner. Please check the Port Number and the SMTP Server (Relay) Name.

Control-M application

Simple Mail Transfer Protocol Parameters Menu
———————————————-

Select one of the following options:

1 – SMTP Server (Relay) Name : mailBR.setaoffice.com
2 – Sender Email : controlm@setaoffice.com
3 – Port Number : 25
4 – Sender Friendly Name : ControlM – Production
5 – Reply-To Email : productioncontrolm@setaoffice.com
6 – Test SMTP Settings

s – Save Parameters

q – Quit

Enter option number —> [q]:6

Testing SMTP Settings…

The SMTP server did not respond in a timely manner.
Please check the Port Number and the SMTP Server (Relay) Name.

Press Enter to continue

Host mailBR.setaoffice.com was being resolved to a different IP address because it was in /etc/hosts file of the server

RHEL 6 server receiving error mounting CIFS (Windows) share – mount error(112): Host is down

When mounting a CIFS (Windows) share, I’m receiving an error saying the host is down

root@linux:~ # mount /mnt/test
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

This is the share in /etc/fstab

root@linux:~ # cat /etc/fstab
//10.0.0.1/CIFS$ /mnt/test cifs _netdev,user=appuser,pass=1234,uid=21376,gid=252,file_mode=0775,dir_mode=0775,domain=windows

I’m running a RHEL 6.9 server

root@linux:~ # cat /etc/*release
LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Red Hat Enterprise Linux Server release 6.9 (Santiago)
Red Hat Enterprise Linux Server release 6.9 (Santiago)

This problem happened because the storage was upgraded and it is using SMB2. You need to have at least kernel 3.7 to have support for SMB2
SMB shares fail to mount with the SMB2 protocol

Linux LVM: File-based locking initialisation failed

Running a lvm command and you encounter the message File-based locking initialisation failed means that the filesystem is read-only

root@linux:~ # pvs
File-based locking initialisation failed

The directory /var/lock/lvm must be writable. So you have a /var or / filesystem read-only.

You can try to remount it as read-write or reboot the server

mount -o remount,rw /
reboot -d -n -f

Source: Running an LVM command returns “File-based locking initialisation failed” or “Locking type 1 initialisation failed”

Linux – shutdown: Unable to shutdown system

Booted the system adding init=/bin/bash at the end of the kernel line.

Entered Rescue system

Now when trying to restart the system, it appears the message shutdown: Unable to shutdown system

bash-4.1# shutdown -r now
shutdown: Unable to shutdown system
bash-4.1# reboot
shutdown: Unable to shutdown system

To reboot the server, you need to use the following command

bash-4.1# reboot -n -d -f

After update to SUSE Linux 11 SP4, it stuck on a black screen written grub>

After updating a Suse Linux 11 to SP4, I’ve booted the server and it was stuck on a black screen written grub>

To solve this problem it is needed to:
Boot using a Suse Linux 11 DVD
Select Rescue System
Choose a language
Login as root

# grub
find /boot/grub/stage1
root (hd0,0) -> type according to your system, found using find /boot/grub/stage1
setup (hd0)
quit

Reboot the server
reboot -d -n -f

%d bloggers like this: