Discuss

discuss@lists.centos.org

8 participants
34745 discussions

tftpd server S not responding
by Asif Iqbal 19 Apr '18

19 Apr '18

I have a tftpd server S running on centos 7 and managed by systemd It is not respoding to A server which is sending the tftp read request RRQ. I do see the RRQ packets coming from A to S, but S never responds back from a different port Y to A So this part is working fine https://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol#/media/File:Tf… But I do not see any attempts to even send a data packet back in my packet capture running on S So this event is not occuring, as if my tftpd server is dead. I have the firewalld turned off on S to eliminate the possibility that firewalld blocking those packets from reeaching to tftpd daemon. I also turned off selinux to eliminate any permission issue. https://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol#/media/File:Tf… I do have tftpd running and managed by systemd $ systemctl status -l tftp ● tftp.service - Tftp Server Loaded: loaded (/etc/systemd/system/tftp.service; indirect; vendor preset: disabled) Active: active (running) since Wed 2018-03-28 18:57:42 UTC; 1min 44s ago Docs: man:in.tftpd Main PID: 1685 (in.tftpd) Memory: 136.0K CGroup: /system.slice/tftp.service └─1685 /usr/sbin/in.tftpd --verbose --verbosity 10 --secure /tftpboot --port-range 4069:4169 Mar 28 18:57:42 S.example.net systemd[1]: Started Tftp Server. Mar 28 18:57:42 S.example.net systemd[1]: Starting Tftp Server... Any help is appreciated! -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

5 14

Enterprise company using CentOS
by Mats Bennsäter 19 Apr '18

19 Apr '18

Hi all We are about to create a business case for migrate RHEL to CentOS for all or a subset of our RHEL holdings. I have two questions that I hope to get help answering. 1. I want to get in touch with a company that have done this journey on an Enterprise company. 2. Suggestion/recommendation of vendors that can provide support for CentOs. Scop: North Europe Number of RHEL +8.000 Support 24x7 Thanks //mats

4 5

Nvidia-detect error with on HP Z4 (CentOS 6.9)
by Danny Smit 17 Apr '18

17 Apr '18

Hi all, I'm testing an installation of nvidia drivers on a HP Z4 workstation (nvidia Quadro P600) with CentOS 6.9. Running nvidia-detect with this setup gives the following output: # nvidia-detect Error getting device_class nvidia-detect also quits with exit-code 255. Could this be a bug in nvidia-detect? Or is it an unsupported configuration? The following hardware is detected, it seems some sort of unknown Intel device is detected by the OS: # lspci | grep VGA 00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4 21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1) # lspci -n | egrep '00:1f.5|21:00.0' 00:1f.5 0000: 8086:a2a4 21:00.0 0300: 10de:1cb2 (rev a1) Tested with the following version (with equal results): nvidia-detect-390.25-1.el6.elrepo.x86_64.rpm nvidia-detect-390.48-1.el6.elrepo.x86_64.rpm -- Regards, Danny

3 6

CentOS 7.4 paniced when running LTP tests
by wuzhouhui 17 Apr '18

17 Apr '18

LTP version: ltp-full-20180118 Kernel version: 3.10.0-693.el7.x86_64 Reproduce procedure: 1. cd ltp-full-20180118; ./configure; make && make install 2. cd /opt/ltp; ./runltp Trace: [ 377.516270] BUG: unable to handle kernel NULL pointer dereference at (null) [ 377.521746] IP: [<ffffffff813510a7>] asn1_ber_decoder+0x327/0xd30 [ 377.525865] PGD 9c6ea067 PUD 66831067 PMD 0 [ 377.529043] Oops: 0000 [#1] SMP [ 377.531454] Modules linked in: ext4 mbcache jbd2 loop ip6t_rpfilter ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter snd_seq_midi snd_seq_midi_event sb_edac edac_core coretemp iosf_mbi crc32_pclmul ghash_clmulni_intel ppdev aesni_intel lrw gf128mul glue_helper ablk_helper cryptd vmw_balloon snd_ens1371 snd_rawmidi snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm dm_mod pcspkr joydev snd_timer nfit sg snd vmw_vmci libnvdimm soundcore [ 377.592112] shpchp i2c_piix4 parport_pc parport ip_tables xfs libcrc32c sr_mod cdrom ata_generic pata_acpi sd_mod crc_t10dif crct10dif_generic vmwgfx drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm crct10dif_pclmul crct10dif_common drm crc32c_intel ata_piix mptspi libata scsi_transport_spi e1000 mptscsih serio_raw mptbase i2c_core [ 377.618291] CPU: 1 PID: 32027 Comm: add_key02 Not tainted 3.10.0-693.el7.x86_64 #1 [ 377.624130] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/02/2015 [ 377.632341] task: ffff880134c8bf40 ti: ffff8800b04c8000 task.ti: ffff8800b04c8000 [ 377.638459] RIP: 0010:[<ffffffff813510a7>] [<ffffffff813510a7>] asn1_ber_decoder+0x327/0xd30 [ 377.645145] RSP: 0018:ffff8800b04cbcc0 EFLAGS: 00010206 [ 377.648925] RAX: 000000000000003f RBX: 0000000000000000 RCX: 0000000000000040 [ 377.653499] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000070 [ 377.659151] RBP: ffff8800b04cbda8 R08: 0000000000019bc0 R09: 0000000000000000 [ 377.663875] R10: 0000000000000002 R11: 0000000000000040 R12: 0000000000000000 [ 377.668679] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 [ 377.673414] FS: 00007f57fc60f740(0000) GS:ffff880139640000(0000) knlGS:0000000000000000 [ 377.678827] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 377.682732] CR2: 0000000000000000 CR3: 00000000a9a11000 CR4: 00000000001407e0 [ 377.687576] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 377.692430] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 377.698824] Stack: [ 377.701875] ffff880139003be8 0000000000000206 0000000000000202 0000000000000202 [ 377.708840] ffff8800b0535080 ffffffff817167c0 ffff8801356da200 000000000000001c [ 377.716247] ffff8801356da200 ffff8800b04cbd00 0000000000000070 ffffffff81716740 [ 377.723168] Call Trace: [ 377.726482] [<ffffffff811df8c6>] ? kmem_cache_alloc_trace+0x1d6/0x200 [ 377.732479] [<ffffffff812eeea1>] x509_cert_parse+0x91/0x120 [ 377.738012] [<ffffffff812efb86>] x509_key_preparse+0x26/0x280 [ 377.743543] [<ffffffff812ee45b>] asymmetric_key_preparse+0x5b/0xd0 [ 377.749370] [<ffffffff812a57a6>] key_create_or_update+0x146/0x460 [ 377.755015] [<ffffffff812a71a9>] SyS_add_key+0x119/0x240 [ 377.760142] [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b [ 377.765606] Code: e0 01 88 85 48 ff ff ff 74 0d 4c 3b 9d 78 ff ff ff 0f 84 99 fd ff ff 48 8b b5 78 ff ff ff 49 8d 43 ff 48 39 f0 0f 86 90 06 00 00 <41> 0f b6 04 34 48 8d 7e 01 48 89 bd 60 ff ff ff 88 45 86 83 e0 [ 377.788713] RIP [<ffffffff813510a7>] asn1_ber_decoder+0x327/0xd30 [ 377.794403] RSP <ffff8800b04cbcc0> [ 377.798198] CR2: 0000000000000000

1 0

rpc.statd is not running but is required for remote locking.
by marcos sr 16 Apr '18

16 Apr '18

Hello I'm trying to mount a nfs system. But i receive this message: mount -t nfs <IP>:/backup /backupnfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified After a fews searchs on google i tried to execute the files: sbin/rpc.statd /usr/sbin/start-statd

3 2

Create CentOS 6 system as "clone" of another - with LVM and different disk sizes
by Toralf Lund 16 Apr '18

16 Apr '18

Hi, I just found myself having to set up a new CentOS 6 system with a nearly identical configuration to an existing host, so I thought I would just 1. Do a minimal install to set up partitions etc. on the new system. 2. Create an image of the existing system using Clonezilla (http://www.clonezilla.org) 3. Run a Clonezilla restore on the new system. - as I though it would be a lot simpler than replicating the exact package selection, installing the same users, doing the same manual config edits (which are required) etc. It turns out that it wasn't quite as easy, though. The problem is that the system use LVM2 volumes for the filesystems, and the new host has a slightly smaller disk than the other, and Clonezilla seems unable to restore to a volume that's smaller than the one that was cloned - even if the actual data fits. I guess I could temporarily reduce the LVM volume sizes on the existing units and clone again, but I'd rather not if I can avoid it. Just copying file-by-file could be an option, too, but I somehow feel less comfortable doing that than the above; there is something about the way I could end up with a mixture of my "minimal install" and the "cloned" data, I suppose. Does anyone have any other ideas about how I might achieve what I want? - Toralf

3 5

Wich is best for backup? nfs of iscsi?
by marcos sr 14 Apr '18

14 Apr '18

Hello I have a CentOS VM with a lots of inodes, and 500GB +/-, running under hyper-v . Which is best for backup them? What is the pros and cons? Thanks for attention.

4 4

YUM4/DNF for CentOS updates announcement
by Marek Blaha 13 Apr '18

13 Apr '18

I am pleased to announce some significant updates to our ConfigManagement Special Interest Group for YUM4. This provides YUM4, based on DNF technology, for testing on CentOS Linux 7/x86_64. These updates are based on feedback from our prior test release last October. It includes signed packages, core DNF plugins, and uses a version of RPM very similar to and compatible with the upcoming version of CentOS 7.5. This initiative is based on a partnership with the upstream YUM and DNF maintainers for the future of package management. Our testing thus far indicates no major problems, but we would love to find out how it fits into your existing YUM 3 workflows. So please consider filling out the short survey - your feedback helps us all get better. YUM 4 provides significant improvements such as fast dependency resolution and a stable, documented API. See the references below for detailed improvements. We have made every effort to preserve the existing end-user experience that is available with YUM 3. This is the primary reason for making YUM 4 available for testing now. For detailed information and instructions to install YUM4 on your CentOS machine, please visit our wiki: https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG/YUM4 And remember to submit feedback in the short survey to help us understand how it can be improved further: https://goo.gl/forms/H1SL1HaEjdV9EUGH3 Many thanks to the CentOS Project team for their assistance in making this happen! Regards, Marek Blaha

1 0

Help with yum
by Paul R. Ganci 13 Apr '18

13 Apr '18

I just did a fresh minimal install of centos 7 on new hardware. While playing around with window systems I removed X windows like so: >yum remove "X Window system" and then tried to re install >yum group install "X Window system" which gives this error: Maybe run: yum groups mark install (see man yum) No packages in any requested group available to install or upgrade I tried running: >yum groups mark install "X Window system" and get the same message. I tried different permutations removing the "s" on groups. Nothing seems to bring back the yum "X Window system" group. Can anyone help me resolve this issue and tell me what I did wrong? Thanks for your help. -- Paul (ganci(a)nurdog.com) Cell: (303)257-5208

5 8

motion
by m.roth＠5-cent.us 12 Apr '18

12 Apr '18

Got a CentOS 7 box running motion. Selinux is complaining that one of the scripts motion runs is mislabeled. Here's what it is. system_u:object_r:nfs_t:s0 /home/motion/bin/on_move_end Now, ~motion is NFS mounted, and we've got use_nfs_home_dirs --> on, so what *would* the proper label be, or do I really need to create a policy for this? mark

1 0

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