Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
On Mon, 15 May 2017 at 20:05 zulu, Frank Thommen wrote: > lustre driver https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/el7.3.1611/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
Hi On 15/05/17 19:30, Tru Huynh wrote: Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? /etc/resolv.conf is 100% ok once I am in the dracut emergency shell and name resolution works fine. However I don't know how it looks at the time of the error message - that is during dracut-initqueue - and I have no idea how I could check that. 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Unfortunateyl not. Due to special hardware (Infiniband, FPGA) and special lustre drivers we are currently bound to this specific release. frank ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru > > 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not > >resolve host: our.centos.mirror; Unknown error curl: (6) Could not resolve host: our.centos.mirror; Unknown error -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B pgp4hccf188iT.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos 7- boot doesn't wait for startup script to complete
On Mon, May 15, 2017 at 04:07:35PM +, KM wrote: > 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 Your systemd service unit is behaving as it would if you didn't specify that user logins couldn't happen until the service had finished. I've done something like this by using a systemd unit that looks like this: (it's a trivial sleep, but you get the idea) # systemctl cat waitcommand.service # /etc/systemd/system/waitcommand.service [Unit] Description=Wait 120 seconds Before=systemd-user-sessions.service [Service] Type=oneshot ExecStartPre=/usr/bin/sleep 120 ExecStart=/usr/bin/logger "Wait finished" TimeoutStartSec=125s KillMode=process [Install] WantedBy=multi-user.target If you try to SSH into the host, you'll get an error like this until the service completes: $ ssh my host System is booting up. See pam_nologin(8) Authentication failed. $ The reason why I have the ExecStartPre is because the service won't be considered "started" until the ExecStartPre command finishes and the ExecStart can run. The unit says that it runs before systemd-user-sessions.service, which is what prevents user logins (and shows the pam_nologin prompt) until it starts. I also set a timeout with a bit longer than the expected time to run. Once my service is started, then user sessions can start. Kinda hacky but it probably will work for you. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] centos 7- boot doesn't wait for startup script to complete
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 To: CentOS mailing list 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 To: CentOS mailing list 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 To: CentOS mailing list 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 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 > To: CentOS mailing list > 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 +, 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 > ___ > 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 ___ 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
[CentOS] plymouth themes problem
Hi all! I was playing with plymouth themes on a c7 box. I found a page on redhat, in their rhel7 documentation that describes how to change to a different plymouth screen: plymouth-set-default-theme --list to find out what themes are installed. then I installed the remaining bunch the yum had available. so then installing one by doing plymouth-set-default-theme dracut -f as documented on the aforementioned page, followed by a reboot produces NO plymouth splash screen. not even if I revert to the system default theme (the "charge" theme). Anybody know what I'm overlooking here? thanks! Fred -- Fred Smith -- fre...@fcshome.stoneham.ma.us - The Lord detests the way of the wicked but he loves those who pursue righteousness. - Proverbs 15:9 (niv) - ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How can kickstart be (re)started manually from the dracut emergency shell?
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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt [...] [ 14.780428] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 19.977052] localhost kernel: tg3 :0b:00.0 eno1: Link is up at 1000 Mbps, full duplex [ 19.977118] localhost kernel: tg3 :0b:00.0 eno1: Flow control is off for TX and off for RX [ 19.978880] localhost kernel: tg3 :0b:00.0 eno1: EEE is disabled [ 19.980693] localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 19.829468] localhost dracut-initqueue[992]: dhcp: PREINIT eno1 up [ 19.853734] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 6 (xid=0x4df19201) [ 26.030151] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 13 (xid=0x4df19201) [ 26.033472] localhost dhclient[1393]: DHCPREQUEST on eno1 to 255.255.255.255 port 67 (xid=0x4df19201) [ 26.033668] localhost dhclient[1393]: DHCPOFFER from 10.128.196.98 [ 26.038851] localhost dhclient[1393]: DHCPACK from 10.128.196.98 (xid=0x4df19201) [ 26.067534] localhost dracut-initqueue[992]: dhcp: BOND setting eno1 [ 28.082735] localhost dhclient[1393]: bound to 10.128.196.20 -- renewal in 21301 seconds. [ 28.456131] localhost kernel: tg3 :0b:00.1: irq 153 for MSI/MSI-X [ 28.456149] localhost kernel: tg3 :0b:00.1: irq 154 for MSI/MSI-X [ 28.456165] localhost kernel: tg3 :0b:00.1: irq 155 for MSI/MSI-X [ 28.456180] localhost kernel: tg3 :0b:00.1: irq 156 for MSI/MSI-X [ 28.456196] localhost kernel: tg3 :0b:00.1: irq 157 for MSI/MSI-X [ 28.570450] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready [ 34.024621] localhost kernel: tg3 :0b:00.1 eno2: Link is up at 1000 Mbps, full duplex [ 34.026347] localhost kernel: tg3 :0b:00.1 eno2: Flow control is off for TX and off for RX [ 34.028069] localhost kernel: tg3 :0b:00.1 eno2: EEE is disabled [ 34.029776] localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno2: link becomes ready [ 33.803606] localhost dracut-initqueue[992]: dhcp: PREINIT eno2 up [ 33.827664] localhost dhclient[1570]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 7 (xid=0x1e8bdc4b) [ 41.000199] localhost dhclient[1570]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 15 (xid=0x1e8bdc4b) [ 55.588353] localhost dhclient[1570]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 18 (xid=0x1e8bdc4b) [ 74.172423] localhost dhclient[1570]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 12 (xid=0x1e8bdc4b) [ 86.446514] localhost dhclient[1570]: DHCPDISCOVER on eno2 to 255.255.255.255 port 67 interval 9 (xid=0x1e8bdc4b) [ 95.253443] localhost dhclient[1570]: No DHCPOFFERS received. [ 95.253648] localhost dhclient[1570]: No working leases in persistent database - sleeping. [ 95.282175] localhost dracut-initqueue[992]: dhcp: FAIL [ 95.353255] localhost dracut-initqueue[992]: RTNETLINK answers: File exists [ 102.502688] localhost dracut-initqueue[992]: Warning: can't find installer mainimage path in .treeinfo [ 102.517568] localhost dracut-initqueue[992]: % Total% Received % Xferd Average Speed TimeTime Time Current [ 102.525942] localhost dracut-initqueue[992]: Dload Upload Total SpentLeft Speed [ 102.534277] localhost dracut-initqueue[992]: 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 1 seconds. 3 retries left. [ 103.527190] localhost dracut-initqueue[992]: 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 2 seconds. 2 retries left. [ 105.533677] localhost dracut-initqueue[992]: 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Transient problem: timeout Will retry in 4 seconds. 1 retries left. [ 109.542329] localhost dracut-initqueue[992]: 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: our.centos.mirror; Unknown error [ 109.551613] localhost dracut-initqueue[992]: Warning: Downloading 'http://our.centos.mirror/7.2.1511/os/x86_64/LiveOS/squashfs.img' failed! [ 109.615143] localhost dracut-initqueue[992]: % Total% Received % Xferd Average Speed TimeTime Time Current [ 109.624698] localhost dracut-initqueue[992]: Dload Upload Total SpentLeft Speed
[CentOS] Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks
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 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mini PCs
Hello Walter, On Mon, 15 May 2017 09:22:54 +0200 "Walter H." wrote: > On Sun, May 14, 2017 11:00, wwp wrote: > > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > > wrote: > > > >> On 13.05.2017 00:29, Robert Moskowitz wrote: > >> > I have been working, for the past few years, with armv7 SOCs and have > >> > a number of servers working. > >> > > >> > Intel, etal are catching up with ARM and I have seen ones like: > >> > > >> > https://www.aliexpress.com/item/NEW-Mini-pc-X86-4-Lan-Qotom-Q190G4N-with-celeron-J1900-quad-core-4-usb-VGA/32785346279.html > >> > > >> > > >> I would take something similar to this: > >> https://www.zotac.com/product/mini_pcs/zbox-ci323-nano > >> (for this zbox I can tell you, that it works with CentOS, as I have one > >> configured as firewall/router) > > > > This might become off-topic with my reply, but I'm curious: is there > > any specific software you're running from CentOS on your zbox in order > > to manage the rooter features? > SSH? I think I've been unclear, sorry about that! I wanted to ask if you use something, any helper installed on this rooter box, on top of firewalld/iptables, in order to setup and administrate the NAT/rooting (and eventually proxy) rules? > > I currently use, between my xDSL box and my LAN machines, an ATX-format > > box running a pretty old GNU/Linux system with a Jay's Firewall setup > > but I'd like to replace it w/ a fanless small barebone like the Zotac > > CI327: ... > this zbox has in comparison to the CI323 a different CPU, which I don't > know if this is supported by CentOS > (I didn't mention, that I use CentOS 6 ...) That's a good point to check, you're right, support for this CPU in either CentOS6 or 7. Regards, -- wwp pgpxuI6dp4ScF.pgp Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mini PCs
On Sun, May 14, 2017 11:00, wwp wrote: > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > wrote: > >> On 13.05.2017 00:29, Robert Moskowitz wrote: >> > I have been working, for the past few years, with armv7 SOCs and have >> > a number of servers working. >> > >> > Intel, etal are catching up with ARM and I have seen ones like: >> > >> > https://www.aliexpress.com/item/NEW-Mini-pc-X86-4-Lan-Qotom-Q190G4N-with-celeron-J1900-quad-core-4-usb-VGA/32785346279.html >> > >> > >> I would take something similar to this: >> https://www.zotac.com/product/mini_pcs/zbox-ci323-nano >> (for this zbox I can tell you, that it works with CentOS, as I have one >> configured as firewall/router) > > This might become off-topic with my reply, but I'm curious: is there > any specific software you're running from CentOS on your zbox in order > to manage the rooter features? SSH? > I currently use, between my xDSL box and my LAN machines, an ATX-format > box running a pretty old GNU/Linux system with a Jay's Firewall setup > but I'd like to replace it w/ a fanless small barebone like the Zotac > CI327: ... this zbox has in comparison to the CI323 a different CPU, which I don't know if this is supported by CentOS (I didn't mention, that I use CentOS 6 ...) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
