Re: [CentOS] Syncronize systemctl status with reality?
Hmmm, that's an interesting option, I'll have to look into it. - Original Message - From: "Alexander Dalloz"To: "centos" Sent: Tuesday, August 29, 2017 4:17:37 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? Am 29.08.2017 um 22:52 schrieb Leroy Tennison: > The AppPreloader is doing things (and probably confusing systemd in the > process) but I didn't start that, it was a part of the reboot. I looked at > /etc/init.d/puppetmaster to see if something strange was being done and it > was one of the simpler init scripts I've seen, uses start-stop-daemon. > > I don't have any control over this, 'systemctl list-unit-files | grep puppet' > shows the puppetmaster.service is enabled, I just need a "cleanup" solution, > any ideas? And, BTW, thanks for any feedback. Remove the Rack Puppet master server. https://docs.puppet.com/puppet/5.1/passenger.html#install-the-puppet-master-rack-application Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Syncronize systemctl status with reality?
Am 29.08.2017 um 22:52 schrieb Leroy Tennison: The AppPreloader is doing things (and probably confusing systemd in the process) but I didn't start that, it was a part of the reboot. I looked at /etc/init.d/puppetmaster to see if something strange was being done and it was one of the simpler init scripts I've seen, uses start-stop-daemon. I don't have any control over this, 'systemctl list-unit-files | grep puppet' shows the puppetmaster.service is enabled, I just need a "cleanup" solution, any ideas? And, BTW, thanks for any feedback. Remove the Rack Puppet master server. https://docs.puppet.com/puppet/5.1/passenger.html#install-the-puppet-master-rack-application Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-virt] Major stability problems with xen 4.6.6
> It seems the patch you mentioned was merged to upstream Linux here: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i > d=71472fa9c52b1da27663c275d416d8654b905f05 > > and then reverted/removed here: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i > d=896d81fefe5d1919537db2c2150ab6384e4a6610 > > Do you know if there has been proper/fixed patch after that? has it been > merged to upstream Linux kernel already? Interesting! I didn't come across that when digging into this. It looks like this hasn't been followed up on at all since April: https://lists.gt.net/engine?list=linux;do=search_results;search_type=AND;sea rch_forum=forum_1;search_string=ldisc%20reopened=post_time Currently I've got ~40 dom0's running with the patch on 4.9.44-39 and it's resolved all stability issues, previously I was seeing multiple crashes a week. Cheers, Nathan ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Syncronize systemctl status with reality?
- Original Message - From: "James Hogarth"To: "centos" Sent: Tuesday, August 29, 2017 2:03:44 PM Subject: Re: [CentOS] Syncronize systemctl status with reality? On 29 Aug 2017 17:58, "Leroy Tennison" wrote: 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 preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master version 3.8.5 Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Could not run: Address already in use - listen(2) Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: PID 1233 read from file /run/puppet/master.pid does not exist or is a zombie. Aug 29 11:24:36 puppetmaster02 systemd[1]: Failed to start Puppet master. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Unit entered failed state. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Failed with result 'resources'. However, ps -ef | grep puppet (run just after the above) returns puppet 1380 1 0 11:26 ? 00:00:08 Passenger RubyApp: /usr/share/puppet/rack/ puppetmasterd root 2015 1341 0 11:48 pts/0 00:00:00 grep --color=auto puppet Earlier ps .. also reported puppet 1355 1166 3 11:26 ? 00:00:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd And, the "bottom line", puppet agent -t on a client works. It reports finishing the catalog run and the client's yaml files on puppetmaster are up to date. Is there a command to tell systemd to re-scan running state and update its understanding on what it finds? I tried systemctl daemon-reload just to be sure that didn't solve the problem before posting this. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos First glance ity looks like someone 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@centos.org https://lists.centos.org/mailman/listinfo/centos OK, something weird is definitely going on here, I have the luxury of rebooting this system so it did. Here's what I got, note the time stamps. ps -ef | grep puppet root 932 1 0 15:23 ?00:00:00 /usr/bin/ruby /usr/bin/puppet master root 1343 1327 0 15:24 pts/000:00:00 grep --color=auto puppet (immediately afterward as fast as I could type:) uptime 15:24:56 up 1 min, 1 user, load average: 0.16, 0.07, 0.02 systemctl status puppetmaster ● puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: activating (start) since Tue 2017-08-29 15:23:44 CDT; 1min 24s ago Control: 932 (puppet) Tasks: 1 Memory: 2.4M CPU: 4ms CGroup: /system.slice/puppetmaster.service └─932 /usr/bin/ruby /usr/bin/puppet master Aug 29 15:23:44 puppetmaster02 systemd[1]: Starting Puppet master... After a short delay: systemctl status puppetmaster ● puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 15:25:11 CDT; 11s ago Process: 932 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 15:23:44 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 15:25:11 puppetmaster02 puppet-master[1360]: Reopening log files Aug 29 15:25:11 puppetmaster02 puppet-master[1360]: Starting Puppet master version 3.8.5 Aug 29 15:25:11 puppetmaster02 puppet-master[1360]: Could not run: Address already in use - listen(2) Aug 29 15:25:11 puppetmaster02 systemd[1]: puppetmaster.service: PID 1360 read from file /run/puppet/master.pid does not exist or is a zombie. Aug 29 15:25:11 puppetmaster02 systemd[1]: Failed to start Puppet master. Aug 29 15:25:11 puppetmaster02 systemd[1]: puppetmaster.service: Unit entered failed state. Aug 29 15:25:11
Re: [CentOS-virt] Major stability problems with xen 4.6.6
Hi, On Thu, Aug 24, 2017 at 03:45:46PM -0700, Nathan March wrote: >Just in case anyone else on this list is running into similar issues, I >can confirm that the patch appears to have resolved this. > > >I've opened [1]https://bugs.centos.org/view.php?id=13713 > > >It was so bad that having the system under load (with rpmbuild) and >opening another ssh window or two would almost always cause the oops. > It seems the patch you mentioned was merged to upstream Linux here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05 and then reverted/removed here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=896d81fefe5d1919537db2c2150ab6384e4a6610 Do you know if there has been proper/fixed patch after that? has it been merged to upstream Linux kernel already? Thanks, -- Pasi > > >Cheers, > >Nathan > > > >From: CentOS-virt [mailto:centos-virt-boun...@centos.org] On Behalf Of >Nathan March >Sent: Wednesday, August 23, 2017 3:32 PM >To: 'Discussion about the virtualization on CentOS' >>Subject: Re: [CentOS-virt] Major stability problems with xen 4.6.6 > > > >This appears to be a centos kernel issue rather than a xen one. > > > >[2]https://lkml.org/lkml/2016/5/17/440 > > > >Digging through the posts and not clear why this never made it upstream... > > > >I'm going to apply that patch to my systems and see if it resolves, but >won't know for certain until a week or two of stability goes by. > > > >- Nathan > > > > > >From: CentOS-virt [[3]mailto:centos-virt-boun...@centos.org] On Behalf Of >Nathan March >Sent: Wednesday, August 23, 2017 2:48 PM >To: [4]centos-virt@centos.org >Subject: [CentOS-virt] Major stability problems with xen 4.6.6 > > > >Hi, > > > >I'm seeing numerous crashes on the xen 4.6.6-1 / 4.6.6-2 releases, on both >the 4.9.34-29 and 4.9.39-29 kernels. > > > >I've attached a txt with two different servers outputs. > > > >Xen-028: This crashed this morning while running 4.6.6-1 and 4.9.39-29 > >Xen-001: This crashed shortly after being upgraded to 4.6.6-2 and >4.9.34-29 > > > >Both are on different hardware platforms, and have had a long history of >being stable until these upgrades. > > > >It sounds potentially related to > > [5]https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound-unstable/+/9ce119f318ba1a07c29149301f1544b6c4bea52a%5E%21/ >but I've confirmed this patch is in the above kernels. > > > >Any suggestions / thoughts? > > > >Cheers, > >Nathan ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Syncronize systemctl status with reality?
On 29 Aug 2017 17:58, "Leroy Tennison"wrote: 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 preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master version 3.8.5 Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Could not run: Address already in use - listen(2) Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: PID 1233 read from file /run/puppet/master.pid does not exist or is a zombie. Aug 29 11:24:36 puppetmaster02 systemd[1]: Failed to start Puppet master. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Unit entered failed state. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Failed with result 'resources'. However, ps -ef | grep puppet (run just after the above) returns puppet 1380 1 0 11:26 ? 00:00:08 Passenger RubyApp: /usr/share/puppet/rack/ puppetmasterd root 2015 1341 0 11:48 pts/0 00:00:00 grep --color=auto puppet Earlier ps .. also reported puppet 1355 1166 3 11:26 ? 00:00:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd And, the "bottom line", puppet agent -t on a client works. It reports finishing the catalog run and the client's yaml files on puppetmaster are up to date. Is there a command to tell systemd to re-scan running state and update its understanding on what it finds? I tried systemctl daemon-reload just to be sure that didn't solve the problem before posting this. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos First glance ity looks like someone 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@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Syncronize systemctl status with reality?
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 preset: enabled) Active: failed (Result: resources) since Tue 2017-08-29 11:24:36 CDT; 22min ago Process: 897 ExecStart=/usr/bin/puppet master (code=exited, status=0/SUCCESS) Aug 29 11:22:39 puppetmaster02 systemd[1]: Starting Puppet master... Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Reopening log files Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Starting Puppet master version 3.8.5 Aug 29 11:24:36 puppetmaster02 puppet-master[1233]: Could not run: Address already in use - listen(2) Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: PID 1233 read from file /run/puppet/master.pid does not exist or is a zombie. Aug 29 11:24:36 puppetmaster02 systemd[1]: Failed to start Puppet master. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Unit entered failed state. Aug 29 11:24:36 puppetmaster02 systemd[1]: puppetmaster.service: Failed with result 'resources'. However, ps -ef | grep puppet (run just after the above) returns puppet 1380 1 0 11:26 ? 00:00:08 Passenger RubyApp: /usr/share/puppet/rack/puppetmasterd root 2015 1341 0 11:48 pts/0 00:00:00 grep --color=auto puppet Earlier ps .. also reported puppet 1355 1166 3 11:26 ? 00:00:01 Passenger AppPreloader: /usr/share/puppet/rack/puppetmasterd And, the "bottom line", puppet agent -t on a client works. It reports finishing the catalog run and the client's yaml files on puppetmaster are up to date. Is there a command to tell systemd to re-scan running state and update its understanding on what it finds? I tried systemctl daemon-reload just to be sure that didn't solve the problem before posting this. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Centos 6 Airprint using CUPS/Avahi
I've set up another airprint server, but this time I've had to use Centos 6 because of the age of the kit I'm using - an old 1U rack server. I've configured CUPS and also Avahi. I've run airprint-generate.py and copied the .service files to /etc/avahi/services/ Everything looks fine until I try to print from my IPhone. I usually test by trying to print an email. As soon as I go to search / select a printer I get the following start to appear in /var/log/cups/error_log E [29/Aug/2017:15:24:07 +0100] Request from "10.1.103.237" using invalid Host: field "harpo.local:631" The printer list appears and I can select a printer and click on print. However nothing prints off, and I just keep getting the above error message. I've tried setting [server] host-name=harpo domain-name=ringways.co.uk in /etc/avahi/avahi-daemon.conf but that just prevents Avahi from starting. Can anyone suggest what I need to do to get Avahi and CUPS to be friendly? Gary -- https://fundraise.cancerresearchuk.org/page/garys-march-march ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ALPN and Http/2, CentOS 7.4
What do you need to serve? Would you think about using Caddy(https://caddyserver.com/) ? It can use the fastcgi interface for php and other related levels of code. Eliezer Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -Original Message- From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of SternData Sent: Sunday, August 27, 2017 02:05 To: CentOS mailing listSubject: [CentOS] ALPN and Http/2, CentOS 7.4 Now that 7.4 CR has delivered OpenSSL 1.0.2, I should be able to serve http/2 pages to Chrome, but I still see messages that ALPN is not enabled. OpenSSL 1.0.2 is installed: $ rpm -qa |grep openssl openssl-libs-1.0.2k-8.el7.x86_64 openssl-1.0.2k-8.el7.x86_64 But https://tools.keycdn.com/http2-test says "www.stevenstern.me" supports http 2 but ALPN is not supported. Ideas? Does anything need to be explicitly enabled for ALPN? As I mentioned, the http2 stuff seems to be working. -- -- Steve ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos