Discuss

discuss@lists.centos.org

11 participants
34747 discussions

Re: [CentOS] centos 7- boot doesn't wait for startup script to complete
by KM 15 May '17

15 May '17

Hello,Nothing I have found has solved this issue. the service starts on boot, but the booting process continues. When I log in my startup script is still running and finishes up. that is good at least, but I'd still like to know how to make it wait. Any feedback is appreciated. Thanks in advance.KM From: KM <info4km(a)yahoo.com> To: CentOS mailing list <centos(a)centos.org> Sent: Tuesday, August 9, 2016 3:38 PM Subject: Re: [CentOS] centos 7- boot doesn't wait for startup script to complete FYI - I just found the following post, https://www.centos.org/forums/viewtopic.php?f=47&t=48140 , which I hadn't seen before. It has to do with adding an entry to rc.local. This has worked for me. I know the correct way would be to set up a systemd service file as I started doing. I will consider all of this while we are supporting different flavors of CentOS/RedHat. Any feedback on this let me know, and as always.... thanks in advance.KM From: KM <info4km(a)yahoo.com> To: CentOS mailing list <centos(a)centos.org> Sent: Tuesday, August 9, 2016 3:07 PM Subject: Re: [CentOS] centos 7- boot doesn't wait for startup script to complete I am taking a step back. I have a normal rc script that is installed with our product. All of the CentOS 7 documentation says the script should work on startup/shutdown. But it doesn't. If I run the script manually it works as it should of course. When I restart the server, nothing happens or starts up. So my question is should it be working as it was without me changing anything? The only way I was able to make it work was to add a service file for it in the systemd directory which is what led to my email in the trail attached below. Any way to see what it is doing? I'll try debugging into out application logs again, but haven't had much luck with that.Thanks in advanceKM From: Jonathan Billings <billings(a)negate.org> To: CentOS mailing list <centos(a)centos.org> Sent: Thursday, August 4, 2016 5:10 PM Subject: Re: [CentOS] centos 7- boot doesn't wait for startup script to complete > On Aug 4, 2016, at 14:35, KM <info4km(a)yahoo.com> wrote: > > thank you for the feedback. I tried using Before=systemd-user-sessions.service. At first glance it seems to work, but then the oracle DB shuts down. Note that myservices starts oracle and then does a few things for our application. > When I remove that entry, it goes right to the login as I originally described, but the oracle DB does not shut down. maybe I have the wrong combination of timeout options with this other option or something, although the timeouts seemed to work also. > Just thought I'd throw it out there. In either case, thanks for helping. > I looked online for an explanation of the options for these files, other that the systemd manual page which is hard to use. I really couldn't find one. Any suggestions? > Thanks again.KM Is your service still a oneshot type? If you are starting daemonized services, systemd is probably terminating them. You should use a 'forking' type for services that will keep around processes. > From: Jonathan Billings <billings(a)negate.org> > To: CentOS mailing list <centos(a)centos.org> > Sent: Tuesday, August 2, 2016 9:28 AM > Subject: Re: [CentOS] centos 7- boot doesn't wait for startup script to complete > >> On Tue, Aug 02, 2016 at 12:56:21PM +0000, KM wrote: >> # used to set up the Myservices onstartup >> [Unit] >> Description=Start and stop Myservices >> >> [Service] >> Type=oneshot >> ExecStart=/etc/init.d/Myservices start >> ExecStop=/etc/init.d/Myservices stop >> RemainAfterExit=yes >> >> [Install] >> WantedBy=multi-user.target > > Reformatting so it is readable. > > What you probably want to do is to add something to the [Unit] section > to make the completion of the be a requirement for the user login > service. Something like: > > Before=systemd-user-sessions.service > > You will most likely also need to add a TimeoutStartSec= to your > [Service] section to give it a longer time to run before systemd times > out the service start. > > > -- > Jonathan Billings <billings(a)negate.org> > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

2 1

How can kickstart be (re)started manually from the dracut emergency shell?
by Frank Thommen 15 May '17

15 May '17

Hi, this is a side question to my other thread regarding dracut-initqueue network issues. Once I'm thrown into a dracut emergency shell (PXE booted system): How can I restart the kickstart installation process manually from there? Can I at all? Background is, that I'd like to add some debugging output to some of the dracut scripts and rerun the installation process to see why it fails. Thanks frank

1 0

Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks
by Son Son 15 May '17

15 May '17

Concern: Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks OS: CentOS 7.3 kernel Version: 3.10.0-514.el7.x86_64 Any IO (write) block size more than 4KiB is split in to number of 4KiB blocks on Centos 7.3 ( where I don't see similar issue on 7.2). I have a setup that involves TWO CentOS 7.3 servers. I tried to run 4MB IO on FC LUN(s) on these servers discovered through Emulex LPe 16000 HBAs. Changed ‘options lpfc lpfc_sg_seg_cn =>1024’ and ‘max_secors_kb =>4MB’ params towards attaining supersize IO ( 4MB block size) , however there are no improvements in getting more than 4K block size IO. There was no impact from these changes. Looking for a help to tune the system to attain supersize IO operation (4MB writes) Regards, Sk

1 0

SCSI drives and Centos 7
by Gregory P. Ennis 14 May '17

14 May '17

Everyone, about 4 years ago, I tried to install CentOS 6 on a Supermicro server with SCSI drives using a LSI raid system. I could never figure out or find a way to make the installation disc of Centos 6 identify the SCSI drives. The installation disc for Centos 5 identified the SCSI drives without a problem. I finally gave up on Centos 6 and installed Centos 5 and the system has worked very well for the last 4 years Now that Centos 5 has been retired, I would like to install Centos 7 on this server. Does the install disc for Centos 7 have the same issues with SCSI drives as Centos 6? Has anyone used Centos 7 on SCSI drives, or am I going to need to get an upgrade of the server? The server is working great. Greg Ennis -- Gregory P. Ennis, M.D., M.R.O. Medical Director EcCare Health Centers www.EcCare.com 972-659-1234

7 13

Virt-Manager and full-screen display
by Nicolas Kovacs 13 May '17

13 May '17

Hi, I have CentOS 7 with Qemu/KVM and Libvirt running on a headless HP Proliant Server. Virtual hosts are managed via Virt-Manager installed on a CentOS 7 + KDE client via SSH. Things are running quite nicely for now, I only have a few small minor details to adjust. On my main workstation running Slackware64 14.1, I also have Qemu/KVM and Virt-Manager installed. When I launch a virtual host and switch to full-screen display, the host is a "real" full screen. But when I do the same thing with CentOS, I don't have a real full-screen display. There's still two grey bars left on the upper and lower end of the screen. Any idea how I can get rid of these and have a 100% full-screen display for a KVM host? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

CentOS 6 / Intel CPU support
by Leon Fauster 12 May '17

12 May '17

https://access.redhat.com/support/policy/intel shows mainly Xeon CPUs. What about Intel Core i7-6700 Quad-Core Skylake has the current EL6 variant support for it? Any experience? Feedback would be greatly appreciated. Thanks, LF

5 8

sshd and problems with network vs NetworkManager
by Gianluca Cecchi 12 May '17

12 May '17

Hello, I'm registering a strange new behavior after updating openssh on my CentOS 7.3 server. Firt of all difference of systemd service configuration between new openssh-server-6.6.1p1-35.el7_3.x86_64 and old openssh-server-6.6.1p1-33.el7_3.x86_6 [root@c7service ~]# diff new_sshd.service old_sshd.service 8c8,9 < Type=notify --- > Type=forking > PIDFile=/var/run/sshd.pid 10c11 < ExecStart=/usr/sbin/sshd -D $OPTIONS --- > ExecStart=/usr/sbin/sshd $OPTIONS 15d15 < RestartPreventExitStatus=255 It changed the Type and it was also added the RestartPreventExitStatus directove. The effects I'm noticing are: 1) If using NetworkManager and no ListenAddress entry in sshd_config --> all ok (listen on ipv4 and ipv6) 2) If using NetworkManager and I put ListenAddress=ip in sshd_config --> all ok 3) If NetworkManager disabled and using only network service and no ListenAddress entry in sshd_config --> ok (listen on ipv4 and ipv6) 4) If NetworkManager disabled and using only network service and I put ListenAddress=ip in sshd_config --> ko with 255 error and so no restart 5) If NetworkManager disabled and using only network service and I put ListenAddress=0.0.0.0 --> ok 6) If NetworkManager disabled and using only network service and I put ListenAddress=ip and comment out the RestartPreventExitStatus line --> ko with 255 error and after 42s restart and ok of sshd Can anyone replicate on an RH EL and report? Do you think I can opena a bugzilla for this or NetworkManager is supposed to be kept running as official support? I have a server with two network interfaces where I want to enable sshd only on the second and I'm blocked if I disable NetworkManager. In the mean time I have commented out the service line related to restart n case of 255 error... I see here that actually 255 is the common exit code for many sshd errors and some discussions about Type of sshd service: https://bugzilla.redhat.com/show_bug.cgi?id=1398360 In changelog of rpm between old and new eleases I only see: * Wed Mar 01 2017 Jakub Jelen <jjelen(a)redhat.com> - 6.6.1p1-35 + 0.9.3-9 - Do not send SD_NOTIFY from forked childern (#1381997) * Fri Feb 24 2017 Jakub Jelen <jjelen(a)redhat.com> - 6.6.1p1-34 + 0.9.3-9 - Add SD_NOTIFY code to help systemd to track running service (#1381997) Thanks in advance, Gianluca

1 0

Thunderbird Regression
by Mark LaPierre 11 May '17

11 May '17

Has anyone else noticed a 10X slowing of the time it takes Thunderbird to load an email that contains graphics on CentOS 6? The last Thunderbird update moved us from Thunderbird 45 to Thunderbird 52. While Thunderbird was loading the images the hard drive was busy cranking out seeks. I have all my local home accounts mounted on a software raid. I solved the problem with a downgrade to Thunderbird 45, but that's a poor solution not keeping Thunderbird up to date with the latest security patches. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 1

TLSv1.3 support?
by Walter H. 11 May '17

11 May '17

Hello, will the next update of CentOS 6 (6.10) have TLSv1.3 support? Thanks, Walter

2 2

Basic authentication - maybe off topoc
by Jerry Geis 11 May '17

11 May '17

Hi - I am using CentOS 7.3 and trying to receive basic authentication. I run a command liked: curl -X POST -u jerry:pw http://192.168.1.8/inbound.cgi When I use printenv in the cgi I do not see the user and password anywhere. Isn't it supposed to be there in an environment variable like REMOTE_USER ? How do I receive the basic authentication ? Thanks, Jerry

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss