search for: tnp

On 01/16/2014 05:10 PM, Ján Tomko wrote: > On 01/16/2014 04:51 PM, hubert depesz lubaczewski wrote: > > What is the address reported by 'netstat -tnp'? Oops, 'nestat -tlnp'. > > Jan >

Hi, First of all, I hope it's not a big problem - I'm running on Debian, not Redhat. To my problem: I'm starting to learn virtualization, libvirt, and decided to create some test machine. I did it with: virt-install --name debian-test \ --os-type=linux \ --os-variant=debianwheezy \ --cdrom /media/media/software/iso/debian-testing-amd64-netinst-2014-01-16.iso \

...the TCP port, virsh domdisplay shows the VNC port, which is the TCP port minus 5900. For graphics listening on the wildcard address, domdisplay always shows 'localhost'. > > But whatever I do - I can't make it to listen on 0.0.0.0. What is the address reported by 'netstat -tnp'? Jan

...ne has started that puppetmaster manually at some point. As such it's not in a cgroup systemd is tracking so it isn't aware of it. Your attempts to start the service are failing because that manually started instance already has the port open. Kill it with pkill -f puppet and then use ss -tnp to check for the port being freed (wait for any time_wait states to go... which is why I'm not filtering by listen). Once it's clear then try starting with systemctl

The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor

...UwBh7WukYMWdoy05ds1Wr1Jo+1aqyKg8mn95b9Nth0p3/7+Vs3CSC3zmnrDxvWNdmC2sMze 1rJ052FyXW+Y3WRYG6l3si7bTCUiXQjbGOTLlvw9dBuyeKc+tloI1rY2vY/sIPHtSH80W9s2 qpDTPdp2pBbeZdCuXyxZZVq7qnxbw44T388madTWxsl+G+MqoszMJrXT5WaZLRFvHPl7+QaG wys19xZxVG+aadRLRrPT2ttV3rzR2qjdQqy9UcXekdb2VAWX3KdB+c6VfONKa6uqoqpfHVPa klLETzOb+tnP/IO8/XVjD1n65eSoPvKn9blXteMebuKxH37bwrRRs/ceFvla8P3WjdmT983p NWcT6RL6xmzit8T1pr76TSv8/DAM4ihssGe2Sw+0D3Mqcr7djNkpis6T2FfxxfdFrOZrv2wR TZX9z+Pa2P1sfik+bmFoZV/0BIZuSWcVD/2H9eabLLszZ/fNi52r9EmL1t17la3GY7tU7tD2 /RYgVeW6bmaSkY7psuFwC9vaNLe7Sz/xUMN2a223tt/YZ2Onjut+7m8NTH+3/qzOhbemHGbP 6xxH6p+JCpzvrV1VJYoD...

...ne has started that puppetmaster manually at some point. As such it's not in a cgroup systemd is tracking so it isn't aware of it. Your attempts to start the service are failing because that manually started instance already has the port open. Kill it with pkill -f puppet and then use ss -tnp to check for the port being freed (wait for any time_wait states to go... which is why I'm not filtering by listen). Once it's clear then try starting with systemctl _______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/li...