Re: [CentOS] Ruby on Cent OS 8
Another option is to migrate to an RHEL 8 -compatible OS, like Rocky Linux, AlmaLinux, Oracle Linux, Springdale Linux. (I remind that CentOS Stream is no more a RHEL 8 twin.) I have already migrated successfully all my CentOS 8 boxes to Rocky. (I am informed that in Academic Institutions in Greece -at least-, SysAdmin teams have also selected Rocky to migrate from CentOS 8.) Rocky seems to be gaining momentum as the main CentOS 8 successor. You may check earlier threads in this mailing list for more info. Cheers, Nick On 8/11/2021 5:06 μ.μ., Josh Boyer wrote: However, CentOS Linux 8 will be going EOL on December 31, 2021. Users are strongly encouraged to migrate to CentOS Stream 8. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Difference between CentOS Linux and CentOS Stream
On 21/7/2021 12:32 π.μ., Ian Mortimer wrote: We've been using the 10 year support to convince researchers to install CentOS instead of their preferred option Ubuntu. We've now lost that argument so most will go to Ubuntu. Those who need 10 year support will move to Oracle. Rocky Linux is here too and it steadily establishes itself as the new standard in terms of a CentOS successor. https://rockylinux.org/news/community-update-june-2021/ Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 9/7/2021 1:14 μ.μ., Gionatan Danti wrote: While I fully understand & agree on the motivation for keeping Rocky (and other clones) 1:1 with Red Hat, it should be understood that current RHEL packages selection itself is drifting away from small/medium business needs. So the core issue is a more fundamental one: Red Hat, our upstream, is walking away from traditional server needs. IMHO, this is a more fundamental discussion, which is beyond future CentOS versions and alternative RHEL-compatible projects and it deserves a separate thread. In any case, I think that the existence and continuous availability / maintenance of external RHEL / CentOS-compatible repositories probably provides a solution for most use scenarios. Of course, I cannot possibly know all actual needs, so I may be wrong. I need to recognize the fact that it appears there is still a shortage of packages for CentOS 8, even though it is active for quite long already. Maybe this is mainly due to EPEL difficulties. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 8/7/2021 8:53 μ.μ., Gionatan Danti wrote: That said, lets face in: current CentOS is not really a community, at least in the sense that a community can steer the project direction. Nobody polled for Stream or asked about it. Stream simply happened due to an unilateral Red Hat decision. *Which is PERFECTLY fine*, unless trying to masking it behind the "community" word. My view is that RH/CentOS would be relatively inadequate for many roles without the outstanding work done by EPEL and the rest of the CentOS community, unless you are an hyperscaler who can do its own internal package additions. Red Hat failing to recognize the enormous value of EPEL and former CentOS model really baffles me. Exactly so. So, this enormous and invaluable effort should not be wasted and abandoned, but should continue and thrive within full community-driven projects like Rocky Linux. This is what I mean by community effort. CentOS is no more a community-driven project, but others emerge. Yet, currently the only one with true community characteristics is probably Rocky Linux. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 8/7/2021 5:46 μ.μ., Leon Fauster via CentOS wrote: Μaybe "we" could fill this gap? Describe this state of EPEL? Did you requested such missing packages? From the early on (EL8.0) I requested such EPEL packages, some fedora maintainers branched there packages into EPEL8. Even a request for a devel package was honored and the rpm was included by RH later in 8.1. This is a community, so communicate! Everything else is a product in ready state that must be paid. +1 In a lot of circumstances we do not invest a bit of time to participate in such community joint efforts and this has a significant cost for all of us in the long run. Let's all be more active in our communities if we want them to remain strong, as Leon suggests. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 8/7/2021 6:53 μ.μ., Valeri Galtsev wrote: THAT must have been part of the reason for mscot. Also, they call mascot Beasty (as in diminutive from :"beast"). And if you pronounce the abbreviation of Berkeley Software Distribution (the one FreeBSD is successor of): BSD, and then "beasty" they sound not that different from one another ;-) That makes things even worse... :( x 2 Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 8/7/2021 6:19 μ.μ., Valeri Galtsev wrote: ... Of course, tastes differ, but still, only those who tasted both things can have fairly say what is better to one's own taste. ... But even as part of our infrastructure fled to FreeBSD... ... As a side note: l never used FreeBSD, even though I've heard good things about it. Frankly, I loathe its devil logo. I know it's probably derived from the Unix "daemons", yet I fail to get reconciled with it. It's simply appalling to me (even if it's smiling) :( I don't require any reply on my above comment (I might even be called naive or whatever). It's some kind of personal confession which I feel I need to express somehow. I simply wish FreeBSD people changed this logo at some point... I wonder whether FreeBSD users are expressing similar concerns... I am not following any FreeBSD activity or discussion. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 7/7/2021 8:17 μ.μ., Valeri Galtsev wrote: And I feel safe running (and planning to run for long future to come) quite reputable ones with long history of such: FreeBSD (servers), Debian (number crunchers, workstations). I feel totally safe and confident with the fully community-driven effort of Rocky Linux, lead by the former founder of the original CentOS project. (I am not affiliated with them in any way.) As has already been mentioned, Rocky Linux has managed to gain quickly support from major players in the industry (including Google and Microsoft), and is committed to never drop its independent/community status. It is well structured and organized, and embraces a good number of open-source volunteer specialists. We want to keep up with RHEL ecosystem and Rocky Linux is - for us - the best option. If some people want to leave the RHEL ecosystem for Debian or FreeBSD, that's OK. But for those who want to stay in the RHEL world, Rocky Linux stands as a rock-solid solution. This opinion does not reject other CentOS clones, but emphasizes the fact that Rocky Linux appears to be a solid option for now and the years to come. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 7/7/2021 12:47 μ.μ., J Martin Rushton via CentOS wrote: There's also Alma, which is where I've gone after being with CentOS since 5.3 AlmaLinux is a great project too, IMHO, but things show that the new industry standard (replacing CentOS) will probably be Rocky Linux. (Yes, RHEL **AND** CentOS have indeed been industry standards - the point of reference -, IMHO, and this is what IBM/RHEL have failed to realize: You don't alter a point of reference.) It is interesting to see what Service Providers will do with their (huge numbers of) CentOS installations, when they migrate... From the users/admins' perspective it is to their interest to have robust and healthy alternatives. In our org, I am now using Rocky Linux on new installations (without issues) and will be migrating several CentOS 8 boxes to Rocky Linux as well. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 30/4/2021 7:27 μ.μ., Gionatan Danti wrote: The correct answer is to buy RH: fine. But do not let Stream touch anything which require a kABI compatible modules. As said above, the Stream move is squarely addresses *cloud* vendor requests and needs. Again, fine. But please leave apart the RH comparison, this is not going to help Stream. Again, don't let me wrong: I wishes the best to Stream, and I will use it where appropriate. But "where" is much smaller today than yesterday. But this aside, I really thank you all CentOS maintainer for your monumental work, and I really hope Stream will be a success. I re-visit this thread, since it is crucial for CentOS 8 users. RESF / Rocky Linux is gaining worldwide recognition and sets itself as the primary organization / platform to become the CentOS 8 heir / successor in the future. Google and Microsoft become RESF sponsors/partners: https://rockylinux.org/news/community-update-june-2021/ And so IBM/RH lose the tremendous advantage they had by owning the CentOS project, which - it seems - never evaluated correctly. From now on, it is clear that hundreds of thousands of CentOS installations will be migrating to Rocky Linux. I also wish the best of success to CentOS Stream, but this is not what the CentOS community expected. My 2c. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] EL8: openldap-servers migration to 389
On 21/6/2021 3:16 μ.μ., Leon Fauster via CentOS wrote: Hey all, in preparation to migrate an EL7 server I noticed that the openldap-servers package is not shipped in EL8 anymore. Is it possible to operate 389-ds as standalone ldap server? I am asking this for the context of CentOS Linux because I read somewhere that 389-ds is mainly used for RHDS only and unsure now about the possibilities to substitute openldap-servers/slapd ... I suggest you to use OpenLDAP packages from here: https://ltb-project.org/download Alternatively, you could use: https://symas.com/symas-providing-openldap-support-redhat-installed-systems/ We have been using ltb-project packages and they work flawlessly for many years (since CentOS 6). Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 28/4/2021 4:28 μ.μ., R C wrote: you think you can fund something like that with a bake sale or so?, maintaining a separate distro for the same thing is VERY expensive I agree, of course, yet it seems that those who decide to maintain a separate distro are decided to do so and obviously are confident that they can handle funding somehow. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 28/4/2021 10:35 π.μ., Nikolaos Milas wrote: All that, in turn, are very much dependent on community involvement and project management & financing. By the way, I think that CentOS, before it was "absorbed" by Redhat, could/might have addressed the community for fund raising, rather than abandoning the project to RH, which, as others have mentioned, was an unmistakable sign of upcoming CentOS EOL as we had come to know it. If the financing need was communicated correctly, I am very confident that financing would have been secured, e.g. by using a public fund raising platform, due to CentOS huge install base and community. Any of those current (or future) projects that might prove successful enough to become CentOS successor (as a RHEL binary twin, and not as Stream), should use the community financing model, in order to avoid CentOS fate. My 0.01$ :) Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos versions in the future?
On 28/4/2021 1:23 π.μ., Gionatan Danti wrote: If the Springdale release is a 100% RH clone, why do different teams (Alma and Rocky) are trying to re-package the same 100% binary-compatible RH clone? Simply because each one of these projects obviously wants to remain independent from the others, otherwise it would request to join forces with one of them. Why they want to remain independent? Due to their vision and internal structure. Check each project's details. Each project's future will be judged by team responsiveness, prompt release availability, product reliability and eventually user adoption. All that, in turn, are very much dependent on community involvement and project management & financing. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Proxmox Backup Server equivalent for the RHEL/CentOS world ?
On 16/4/2021 10:10 π.μ., Felix Kölzow wrote: you may take a look at _rear_ (it is that easy how it looks like) You may also want to check mondo: http://www.mondorescue.org/about.shtml (the website is not updated regularly!) I am using it for many years, since CentOS 5 (until now with CentOS 8). There may be a few glitches, but otherwise I am pretty satisfied. It supports bare metal recovery and can be used for cloning too. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] not a Centos topic, but since many had concerns ......
On 3/2/2021 1:26 π.μ., R C wrote: The reason why I have some Centos stuff is because it is very close to Redhat, and where I work we use A LOT of redhat machines/servers/clusters, so it is just convenience. That is why I used Centos, and if this mechanism/program is available, well, I'll use that. If you want free/open-source alternative to good old CentOS for full RHEL compatibility, my 2c is to wait for Rocky Linux, the successor of CentOS, a project started by CentOS original founder: it's now brewing, it will be available end of March: Check https://wiki.rockylinux.org/ Also, look at almalinux.org, also brewing: https://almalinux.org/ There is also (already available): Springdale Linux http://springdale.math.ias.edu/ Oracle Linux is also an option but I don't fancy projects orchestrated by big corporations. Personally, I feel closer to the first one (Rocky Enterprise Linux: R_EL!). Soon, we'll know. It comes to my mind that IBM/RH recently offered more options for free RHEL subscriptions in order to make it more difficult to the community to build and maintain projects like the above by dissipating CentOS community (leveraging CentOS Stream too). Probably CentOS acquisition itself was aiming at CentOS project cancellation, as we know it. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL changes
On 22/1/2021 2:25 μ.μ., Konstantin Boyandin via CentOS wrote: Also, I can still expect they will again change their mind close to 2021's end. In short, I have hard time trusting RH in such a situation. That's exactly how I feel too. I don't trust them. I think we can expect Rocky Linux to provide a real solution to CentOS future. We shall know very soon, so let's just wait for a short while. There is such a huge (staggering) number of CentOS installed base, esp. including service providers (hosts etc.), that the market NEEDS a real reliable successor of CentOS. This need cannot be covered by RHEL new licensing. A real open source, community solution will be needed; for the time being, Rocky Linux seems to have the right specs to fill the gap. The market itself will finance (through donations) its future, because it is a real need. A CentOS successor is a real need. OL will be last resort, but I believe Rocky Linux will most probably be the way to go. It displays good momentum, steady progress and great manpower. My 2c. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL changes
On 21/1/2021 11:17 μ.μ., Valeri Galtsev wrote: I tried Oracle Linux. After installation it took forever to update yum database, or do you yum search. Also: I didn't find mirrors... All this sort of ruled it out for me. Don't worry, Rocky Linux is in good track; Latest update: https://forums.rockylinux.org/t/community-update-january-2021/1667 It will be with us very soon, and the formerly CentOS community is very active on it! I am very optimistic with it. RH is trying to catch all those CentOS users/admins who will jump off the train to shift to Rocky Linux (or other), but I think Rocky Linux will become the natural successor. The future is close, we shall see. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Stream suitability as a production webserver
On 8/1/2021 11:01 π.μ., Fabian Arrotin wrote: With my SysAdmin hat on, I'd say that the only real impacting bit is the shorter lifetime (5y instead of 10), but with overlap between stream versions, so one would have time to have a look, reflect in automation, reinstall/migrate, enjoy With my sysadmin hat on, I'd say wait for a bit of time for Rocky Linux (or whatever will be finally called) or Lenix to mature and check adoption, and if not satisfied (which I consider unlikely) move to Oracle Linux. Just forget all this cooking with Stream. If you wear another hat, you can see things differently, but as a sysadmin, to me the above course of action is clear. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] The conclusio: CentOS is dead
On 15/12/2020 12:47 π.μ., Ruslanas Gžibovskis wrote: your suggestions? My course of action is to wait for Lenix (Ref.: https://blog.cloudlinux.com/announcing-open-sourced-community-driven-rhel-fork-by-cloudlinux) and Rocky Linux (https://rockylinux.org/) by CentOS original founder. IMHO, both will end to what we really want/need, because they care. As I have already mentioned, I would encourage projects to join forces to produce a single platform. I won't go to Ubuntu, Debian, FreeBSD. You may call it a personal preference. I feel much more comfortable with EL. I would try to avoid OL (as it is governed by a large corp which can drop it easily). Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I'm looking forward to the future of CentOS Stream
On 13/12/2020 9:44 μ.μ., Simon Avery wrote: There are 4,606 people on their Slack right now ...which, by the way, is being acquired by SalesForce! Find a successor of Slack! Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Announcing Open-sourced & Community-Driven RHEL Fork by CloudLinux
On 13/12/2020 1:05 μ.μ., Ljubomir Ljubojevic wrote: Just an update, name of the project will be "Lenix", and I missedin announcement that unlike CentOS they plan to publish all the build tools and environment so other clones can be built even if they stray, a very commendable approach. Sounds great! It comes to mind that if Lenix and RockyLinux (and possibly other major forces) could merge and join efforts as a common project, the project could gain tremendous momentum very fast. As was earlier mentioned, it is not easy to maintain such projects in the long term (despite goodwill), so joining forces would be quite safer for both the projects and the community, while it would also keep the community more focused, avoiding to disperse in multiple distros. In any case, this is the kind of projects we would want to see, rather than large corporations' clones like OL. And what I like is that there is so much energy in the CentOS community, that so important new projects are being announced in day zero after CentOS suicidal turn to Stream. I am very confident that CentOS will live and prosper, but with a different name! (Unless IBM/RH **immediately** withdraw their announced plans and course of action.) Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] I'm looking forward to the future of CentOS Stream
On 13/12/2020 6:48 π.μ., Gordon Messmer wrote: Red Hat is giving us the thing that has been requested more often, by more people, than any other change in CentOS, and the result is that the press is full of stories about users being angry, because five people on the mailing lists sent a lot of messages. (About half of the traffic in the threads on centos and centos-devel comes from five people, and various people replying to them.) Not really. I am afraid you are missing the point. Also see: 7500 sysadmins and growing are already explicitly rejecting the change. ...but speaking as a developer... That's the problem: you are speaking as a developer, not as a sysadmin. CentOS is clearly for sysadmins, not for developers. On 13/12/2020 10:22 π.μ., Nicolas Kovacs wrote: For the last 16 years, the explicit scope of the CentOS project has been to rebuild RHEL "bug by bug". No more no less. A fact that has been stressed repeatedly by the maintainers on this list. So admins all over the world trusted this. Words do have a meaning. +1 And what is worse: RH are pushing their users to their competitors (read: OL). RH are pulling their own eyes out... It's a shame. And all that because they decided to stop supporting a quite extensive worldwide amount of orgs and sysadmins who need a safe and dependable production OS that does not cost a fortune, although many of those at some point in time might become RH support customers! Now RH earned discontent and distrust from a large part of their FOSS community. Such a sad end for CentOS... (In fact it is an end indeed.) OL, Rocky Linux (when fully established) and other such projects (mentioned in various threads) will gain large parts of this extensive group. Some many end up in using CentOS Stream, but the core part of this vibrant community will probably lost by RH and the good old CentOS group (now in RH). Time will show. That's a pity, because a large and conscious part of this community indeed has some affinity to Karanbir et al, greatly respecting their history and efforts... RH (& CentOS) still has some small window of opportunity to announce full support of CentOS 8 to its EOL. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 Stream: The Good, The Bad, The Ugly
On 10/12/2020 2:39 μ.μ., Steve Thompson wrote: On Wed, 9 Dec 2020, Joshua Kramer wrote: It can, however, be mitigated if RedHat backtracks, admits their mistake, and affirmatively commits to support future CentOS point releases. I'll be interested to see how this turns out. It may already be too late. Even if RedHat says "my bad" and goes back on this decision, not many will trust them in the future. Even so, it's the least they are expected to do. Just say "OK, we are having our company planning, but our planning and operations are deeply affected by our community, so we cannot remain indifferent to their loud feedback; we shall support CentOS 8 as initially announced for its complete life-cycle and we guarantee that officially." If they shut their ears to to the whole world, it's an even bigger mistake. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/
On 9/12/2020 4:32 μ.μ., Brendan Conoboy wrote: As CentOS Stream grows, I expect many companies who sell hardware will become active members of the community. Probably, but this is not the point. The value of CentOS is that in essence it is identical to RHEL. This allows its use in multiple scenarios which the new CentOS Stream will not be able to support any more, due to its nature. You may want to read comments at: https://blog.centos.org/2020/12/future-is-centos-stream/ and: https://www.change.org/p/centos-governing-board-do-not-destroy-centos-by-using-it-as-a-rhel-upstream to realize why this change will make it unsuitable in most of its current usage scenarios. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 future
On 9/12/2020 3:19 μ.μ., Nikolaos Milas wrote: I still hope that you will not disappoint CentOS admins and users so badly and that you will continue to support CentOS 8 (and CentOS 7) in its current/expected form. A petition has started, to request IBM/Redhat to continue CentOS 8 as initially announced/promised. Those who agree, are urged to sign: https://www.change.org/p/centos-governing-board-do-not-destroy-centos-by-using-it-as-a-rhel-upstream Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 future
On 8/12/2020 6:58 μ.μ., Satish Patel wrote: What is going on here https://blog.centos.org/2020/12/future-is-centos-stream/ CentOS 8's future is not looking bright. Recently deployed CentOS8 on my production workload and now hearing this. What do other folks think about this? I will totally agree with the following comments on the above blog article: "Matt Phelps says (December 8, 2020 at 4:12 pm): This is a breach of trust from the already published timeline of CentOS 8 where the EOL was May 2029. One year's notice for such a massive change is unacceptable. Move this approach to CentOS 9." and: "fahrradflucht says (December 8, 2020 at 5:37 pm): This! People already started deploying CentOS 8 with the expectation of 10 years of updates. - Even a migration to RHEL 8 would imply completely reprovisioning the systems which is a big ask for systems deployed in the field." You people at IBM/RedHat are betraying and crucifying your own users and community, right after we have started numerous CentOS 8 systems in production, after months or even years of planning, investing in know-how and testing. This is really irritating. If you do not recall this policy, not only you will cause huge problems to thousands of administrators out there; you will suffer their wrath. Unless you recall this policy and provide CentOS 8 as promised until the end of its life-cycle, you are proving imposters by luring thousands to using a product which you planned to effectively abolish. I still hope that you will not disappoint CentOS admins and users so badly and that you will continue to support CentOS 8 (and CentOS 7) in its current/expected form. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] nfs causes Centos 7.7 system to hang
Hello, MERRY CHRISTMAS to all in list! After I upgraded to latest: CentOS Linux release 7.7.1908 (Core) I am facing nfs crashes which cause the system to hang frequently. This is caused by cp to nfs-mounted shares. Below is dmesg output; you will see call traces. These cause system to gradually overload: [root@hesperia1 ~]# top top - 10:09:40 up 10:16, 1 user, load average: 53.66, 54.13, 52.98 Tasks: 475 total, 2 running, 436 sleeping, 0 stopped, 37 zombie %Cpu(s): 0.1 us, 0.6 sy, 0.0 ni, 99.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.1 st KiB Mem : 3879928 total, 813504 free, 1733216 used, 1333208 buff/cache KiB Swap: 4063228 total, 4062708 free, 520 used. 1797264 avail Mem and finally hangs showing messages (which I have not recorded precisely) in the CLI login screen like "System out of memory". Then I have to reboot. I tried to downgrade nfs-utils and rpcbind to earlier versions (in case there is a bug in latest ones), but I couldn't: [root@hesperia1 ~]# yum downgrade rpcbind-0.2.0-47 nfs-utils-1.3.0-61 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: ftp.ntua.gr * epel: mirrors.daticum.com * extras: ftp.ntua.gr * updates: ftp.ntua.gr No package rpcbind-0.2.0-47 available. No package nfs-utils-1.3.0-61 available. Error: Nothing to do Do you know if this is a known bug? (I couldn't find something in my searches.) Can you suggest a solution / workaround? I am facing this problem constantly and the system has become unstable. [root@hesperia1 ~]# dmesg ... [ 26.525584] RPC: Registered named UNIX socket transport module. [ 26.525588] RPC: Registered udp transport module. [ 26.525590] RPC: Registered tcp transport module. [ 26.525592] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 27.103268] type=1305 audit(1577317991.465:3): audit_pid=836 old=0 auid=4294967295 ses=4294967295 res=1 [ 29.384755] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 29.629701] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 30.773604] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 31.977476] FS-Cache: Loaded [ 32.170682] FS-Cache: Netfs 'nfs' registered for caching [ 53.671997] random: crng init done [26399.967630] INFO: task cp:14560 blocked for more than 120 seconds. [26399.967984] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [26399.968202] cp D 89373fc9ac80 0 14560 14053 0x0080 [26399.968211] Call Trace: [26399.968272] [] ? nfs_permission+0x105/0x220 [nfs] [26399.968321] [] ? security_inode_permission+0x22/0x30 [26399.968345] [] schedule_preempt_disabled+0x29/0x70 [26399.968375] [] __mutex_lock_slowpath+0xc7/0x1d0 [26399.968395] [] ? unlazy_walk+0x133/0x140 [26399.968404] [] mutex_lock+0x1f/0x2f [26399.968410] [] lookup_slow+0x33/0xa7 [26399.968421] [] path_lookupat+0x838/0x8b0 [26399.968445] [] ? kmem_cache_alloc+0x35/0x1f0 [26399.968475] [] ? getname_flags+0x4f/0x1a0 [26399.968481] [] filename_lookup+0x2b/0xc0 [26399.968487] [] user_path_at_empty+0x67/0xc0 [26399.968492] [] ? cp_new_stat+0x165/0x1a0 [26399.968497] [] user_path_at+0x11/0x20 [26399.968501] [] vfs_fstatat+0x63/0xc0 [26399.968505] [] SYSC_newstat+0x2e/0x60 [26399.968530] [] ? __audit_syscall_exit+0x1e6/0x280 [26399.968534] [] SyS_newstat+0xe/0x10 [26399.968544] [] system_call_fastpath+0x25/0x2a [27479.967352] INFO: task cp:4656 blocked for more than 120 seconds. [27479.967414] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [27479.967711] cp D 8936b6548000 0 4656 2914 0x0080 [27479.967726] Call Trace: [27479.967749] [] ? nfs_permission+0x105/0x220 [nfs] [27479.967762] [] ? security_inode_permission+0x22/0x30 [27479.967769] [] schedule_preempt_disabled+0x29/0x70 [27479.967774] [] __mutex_lock_slowpath+0xc7/0x1d0 [27479.967786] [] ? unlazy_walk+0x133/0x140 [27479.967792] [] mutex_lock+0x1f/0x2f [27479.967821] [] lookup_slow+0x33/0xa7 [27479.967828] [] path_lookupat+0x838/0x8b0 [27479.967836] [] ? kmem_cache_alloc+0x35/0x1f0 [27479.967841] [] ? getname_flags+0x4f/0x1a0 [27479.967846] [] filename_lookup+0x2b/0xc0 [27479.967852] [] user_path_at_empty+0x67/0xc0 [27479.967857] [] ? cp_new_stat+0x165/0x1a0 [27479.967862] [] user_path_at+0x11/0x20 [27479.967866] [] vfs_fstatat+0x63/0xc0 [27479.967870] [] SYSC_newstat+0x2e/0x60 [27479.967880] [] ? __audit_syscall_exit+0x1e6/0x280 [27479.967884] [] SyS_newstat+0xe/0x10 [27479.967892] [] system_call_fastpath+0x25/0x2a [27479.967910] INFO: task cp:7754 blocked for more than 120 seconds. [27479.968147] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [27479.968437] cp D 89373fc1ac80 0 7754 7285 0x0080 [27479.968443] Call Trace: [27479.968455] [] ? nfs_permission+0x105/0x220 [nfs] [27479.968461] [] ? security_inode_permission+0x22/0x30 [27479.968466] []
Re: [CentOS] How to dump/restore a CentOS 7 system
On 25/9/2019 7:31 μ.μ., Xinhuan Zheng wrote: I guess it is very common for administrative purpose, to dump and restore a CentOS 7 system. I usually use dump/restore commands. However, I’m having trouble to handle installing bootloader and creating initramfs for C7 system. Does anyone know a good document source that details those procedure? I am using mondorescue (mondoarchive, mondorestore) for years with success: http://www.mondorescue.org/ Allows bare metal recovery. I have tested and it works fine in CentOS 5,6,7. In CentOS 7, after restore, I have had some issues, but I managed to resolve them. (Details in mailing list archives.) Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 7/10/2017 7:35 μμ, Nikolaos Milas wrote: I am still trying to find a solution. The problem was finally traced down to a Cisco ASA bug (this firewall device lies between the connected networks); bug CSCuq80704 was resolved by an ASA software update. NFS packets were incorrectly being dropped by ASA and were causing nfs traffic to stall. After ASA software upgrade the problem has not occurred again. I can't tell why this was not happening for many months, but only lately. Case closed. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 4/10/2017 3:09 μμ, Nikolaos Milas wrote: Problem solved - at least in my case - by changing the NFS Export Options (of the NFS shared directory, at the data storage system) from secure to insecure. In the end, it occurred that the issue re-appeared after a couple of days. So, it seems that this change did not actually solve the problem. I am still trying to find a solution. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 2/10/2017 11:46 μμ, Nikolaos Milas wrote: Unfortunately, it doesn't work for me. Problem solved - at least in my case - by changing the NFS Export Options (of the NFS shared directory, at the data storage system) from secure to insecure. That is, I changed from: rw,no_root_squash,no_all_squash,secure,nolog to: rw,no_root_squash,no_all_squash,insecure,nolog I don't know if the behavior I had described can be explained by using the "secure" option, but after I changed to "insecure" everything works fine, using the latest packages - latest kernel and latest rpms. If anyone can provide some insight on it, that would be appreciated (since I know little about NFS). Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 2/10/2017 11:19 πμ, Patrick Begou wrote: This config is working fior me, with just using an older kernel. Thanks Patrick, Unfortunately, it doesn't work for me. I tried booting with an older kernel (3.10.0-514.21.1.el7.x86_64) and/or downgrading rpcbind to rpcbind-0.2.0-38.el7.x86_64 (all three combinations: each one separately and both at the same time), but it didn't work. I have not tried to downgrade nfs-utils as well... Note that on the same VLAN, on the same cluster, I have another VM which I have not upgraded yet (thankfully) to 7.4 and this works normally (using 7.3 and rpcbind-0.2.0-38.el7). My findings and logs are available at: https://bugzilla.redhat.com/show_bug.cgi?id=1494834 Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 22/9/2017 8:15 μμ, Nikolaos Milas wrote: I have created bug report: https://bugs.centos.org/view.php?id=13891 for this. I have also created https://bugzilla.redhat.com/show_bug.cgi?id=1494834 and I have uploaded a lot of (hopefully useful) information, but there doesn't seem to exist any activity on the issue nor have I had any feedback, although it's been a week since the report. I continue to have this issue. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 22/9/2017 3:46 μμ, Nikolaos Milas wrote: Based on the facts and experience, it looks like a bug. After all, it occurred right after upgrade to 7.4, without any system configuration changes. I have created bug report: https://bugs.centos.org/view.php?id=13891 for this. Isn't there anyone else having NFS mount issues after upgrade to 7.4? (I have found this report: https://access.redhat.com/solutions/3146191 which I think is not directly related.) Other possible error report which could be related: https://www.reddit.com/r/ansible/comments/6tu9c4/mounting_a_nfs_share_from_aix_to_rhel_74_remote/dlpdco6/?st=j7w56e1a=065301d7 Please let me know if there can be a workaround or something. Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 22/9/2017 2:58 μμ, Nikolaos Milas wrote: ... or through /etc/fstab: 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 Correction: the /etc/fstab nfs mount line has one more zero: 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 I am looking forward to your feedback. Based on the facts and experience, it looks like a bug. After all, it occurred right after upgrade to 7.4, without any system configuration changes. Please help! Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 2/6/2017 1:46 μμ, Nikolaos Milas wrote: After a bit of search, I found the associated reports: https://bugs.centos.org/view.php?id=13351 https://bugzilla.redhat.com/show_bug.cgi?id=1454876 No solution yet, but -as a workaround- it seems that -at least- nfs problems are indeed solved with downgrading. I have been working fine with CentOS 7.3, since I downgraded to rpcbind-0.2.0-38.el7.x86_64. Today, I decided to upgrade to 7.4 (which, among several hundred updates, includes rpcbind-0.2.0-42.el7.x86_64); after that I have started having similar NFS issues again: NFS communication hungs. In /var/log/messages: - ... Sep 22 11:03:21 hesperia1 kernel: RPC: Registered named UNIX socket transport module. Sep 22 11:03:21 hesperia1 kernel: RPC: Registered udp transport module. Sep 22 11:03:21 hesperia1 kernel: RPC: Registered tcp transport module. Sep 22 11:03:21 hesperia1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Sep 22 11:03:21 hesperia1 systemd-udevd: starting version 219 Sep 22 11:03:21 hesperia1 systemd: Started Configure read-only root support. Sep 22 11:03:21 hesperia1 kernel: Installing knfsd (copyright (C) 1996 o...@monad.swb.de). Sep 22 11:03:21 hesperia1 systemd: Mounted NFSD configuration filesystem. ... Sep 22 11:03:27 hesperia1 systemd: Mounting /mnt/dd2500-1... Sep 22 11:03:27 hesperia1 systemd: Starting Notify NFS peers of a restart... Sep 22 11:03:27 hesperia1 sm-notify[948]: Version 1.3.0 starting Sep 22 11:03:27 hesperia1 systemd: Started Notify NFS peers of a restart. Sep 22 11:03:27 hesperia1 systemd: Started OpenSSH server daemon. Sep 22 11:03:27 hesperia1 kernel: FS-Cache: Loaded Sep 22 11:03:27 hesperia1 kernel: FS-Cache: Netfs 'nfs' registered for caching Sep 22 11:03:27 hesperia1 systemd: Mounted /mnt/dd2500-1. Sep 22 11:03:27 hesperia1 systemd: Reached target Remote File Systems. Sep 22 11:03:27 hesperia1 systemd: Starting Remote File Systems. ... Sep 22 11:11:16 hesperia1 kernel: nfs: server 10.201.40.34 not responding, still trying ... Sep 22 11:20:44 hesperia1 kernel: nfs: server 10.201.40.34 not responding, still trying ... - I tried downgrading to rpcbind-0.2.0-38.el7.x86_64 but this time it didn't help. I mount either directly: mount -vv -o auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 -t nfs 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 or through /etc/fstab: 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 The box may even hung during reboot, which has never happened in the past. It needs a hard reboot (via VM admin console) to boot again. I have confirmed the above behavior multiple times. Please advise me on how to resolve this situation. We are very much dependent on NFS mounts. Is it a known bug? (As far as I could search, I didn't came up with something.) The earlier bug report appears resolved: https://bugzilla.redhat.com/show_bug.cgi?id=1454876 Can I safely/easily revert to 7.3? Thanks in advance, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Troubleshooting php-fpm with apache on Centos 7
On 8/8/2017 9:16 πμ, Nikolaos Milas wrote:
For your reference, I am also including the php-fpm configuration
I now browsed today's php-fpm log file (/var/log/php-fpm/www-error.log -
which is rotated daily) and I found two PHP records about this website,
with the following content:
--
...
[08-Aug-2017 05:11:45 Europe/Athens] PHP Fatal error: Uncaught Error:
Call to undefined function get_header() in
/var/webs/wwwgreekgeo/www/wp/wp-content/themes/nirvana/404.php:10
Stack trace:
#0 {main}
thrown in
/var/webs/wwwgreekgeo/www/wp/wp-content/themes/nirvana/404.php on line 10
[08-Aug-2017 05:11:45 Europe/Athens] PHP Fatal error: Uncaught Error:
Call to undefined function get_header() in
/var/webs/wwwgreekgeo/www/wp/wp-content/themes/nirvana/404.php:10
Stack trace:
#0 {main}
thrown in
/var/webs/wwwgreekgeo/www/wp/wp-content/themes/nirvana/404.php on line 10
...
It appears as a single entry recorded twice (for some unknown reason).
So, even this one (double) entry means that THERE IS (at least some) PHP
logging about this website!
But there are many questions:
- Why there is only one error entry about this website (in the last two
and a half days)?
- Why is it double?
- Why there is nothing else (PHP-related) logged about this website?
- Why no other debugging info is being logged?
- Could php-fpm somehow be "blacklisting" the website PHP application
(WordPress) due to this (and possible other) errors?
Any ideas?
Thanks,
Nick
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Troubleshooting php-fpm with apache on Centos 7
On 8/8/2017 8:57 πμ, John R Pierce wrote: does the user apache is running as have write access to that folder ? Thank you for your reply, John. Yes, there is write access: # ls -l /var/webs/wwwgreekgeo/log/php* -rw-rw 1 root apache 0 Aug 7 22:58 /var/webs/wwwgreekgeo/log/php_error_log # ls -l /var/webs/wwwgreekgeo/ total 8 drwxrwx--- 2 wftpuser apache 4096 Aug 8 03:46 log drwxrwx--- 10 wftpuser apache 4096 Dec 5 2014 www For your reference, I am also including the php-fpm configuration: # cat /etc/php-fpm.d/www.conf include=/etc/php-fpm.d/*.conf [global] pid = /run/php-fpm/php-fpm.pid error_log = /var/log/php-fpm/error.log log_level = debug daemonize = yes [www] user = apache group = apache listen = 127.0.0.1:9000 listen.allowed_clients = 127.0.0.1 pm = dynamic pm.max_children = 50 pm.start_servers = 2 pm.min_spare_servers = 2 pm.max_spare_servers = 4 pm.process_idle_timeout = 10s; pm.max_requests = 500 pm.status_path = /fpm-status slowlog = /var/log/php-fpm/www-slow.log request_slowlog_timeout = 5s request_terminate_timeout = 20s catch_workers_output = yes security.limit_extensions = .php .php3 .php4 .php5 .php7 .htm .html php_admin_value[error_log] = /var/log/php-fpm/www-error.log php_admin_flag[log_errors] = on php_value[session.save_handler] = files php_value[session.save_path]= /var/lib/php/session php_value[soap.wsdl_cache_dir] = /var/lib/php/wsdlcache php_admin_value[post_max_size] = 40M php_admin_value[short_open_tag] = On php_value[date.timezone] = "Europe/Athens" Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Troubleshooting php-fpm with apache on Centos 7
Hello,
I am running httpd-2.4.6-45.el7.centos.x86_64 with
php-fpm-7.0.22-1.el7.remi.x86_64 (on CentOS 7).
My main problem: On this httpd server I have several vhosts running, but
apparently I am facing intermittent problems with php-fpm communication
on only one of them.
Most of the sites are WordPress or Joomla Applications (running with
mysql). Everything seems right: low load, all websites are operating
fine, except this one, but only intermittently.
The secondary problem is that I can't seem to be able to log php errors.
When the problem starts, the users receive "503 Service Unavailable"
pages for many hours/days, and in the error log I see only such errors:
[Tue Aug 08 08:27:31.742640 2017] [proxy_fcgi:debug] [pid 29259]
mod_proxy_fcgi.c(963): [client 180.76.15.139:30619] AH01076: url:
fcgi://127.0.0.1:9000/var/webs/wwwgreekgeo/www/wp/index.php
proxyname: (null) proxyport: 0
[Tue Aug 08 08:27:31.742642 2017] [proxy_fcgi:debug] [pid 29259]
mod_proxy_fcgi.c(970): [client 180.76.15.139:30619] AH01078: serving
URL fcgi://127.0.0.1:9000/var/webs/wwwgreekgeo/www/wp/index.php
[Tue Aug 08 08:27:31.742645 2017] [proxy:debug] [pid 29259]
proxy_util.c(2203): AH00942: FCGI: has acquired connection for (*)
[Tue Aug 08 08:27:31.742661 2017] [proxy:debug] [pid 29259]
proxy_util.c(2256): [client 180.76.15.139:30619] AH00944: connecting
fcgi://127.0.0.1:9000/var/webs/wwwgreekgeo/www/wp/index.php to
127.0.0.1:9000
[Tue Aug 08 08:27:31.742690 2017] [proxy:debug] [pid 29259]
proxy_util.c(2422): [client 180.76.15.139:30619] AH00947: connected
/var/webs/wwwgreekgeo/www/wp/index.php to 127.0.0.1:9000
[Tue Aug 08 08:27:31.742739 2017] [proxy:debug] [pid 29259]
proxy_util.c(2798): AH02824: FCGI: connection established with
127.0.0.1:9000 (*)
[Tue Aug 08 08:27:52.347960 2017] [proxy_fcgi:error] [pid 29259]
(104)Connection reset by peer: [client 180.76.15.139:30619] AH01075:
Error dispatching request to :
[Tue Aug 08 08:27:52.348021 2017] [proxy:debug] [pid 29259]
proxy_util.c(2218): AH00943: FCGI: has released connection for (*)
The problem is NOT resolved by restarting apache and/or php-fpm.
The config of the vhost is as follows:
DocumentRoot "/var/webs/wwwgreekgeo/www"
ServerName www.greekgeo.noa.gr
ServerAdmin webmas...@noa.gr
DirectoryIndex index.php index.html index.htm
php_flag log_errors on
php_flag display_errors off
php_value error_log /var/webs/wwwgreekgeo/log/php_error_log
#php_value error_reporting 32767
#php_value error_reporting 2147483647
php_value error_reporting 6135
Redirect 301 /en.index.html http://www.greekgeo.noa.gr/wp/
RewriteEngine on
RedirectMatch ^/index.html$ /wp/
Options -Indexes +FollowSymLinks
AllowOverride All
Require all granted
Require all denied
SetHandler "proxy:fcgi://127.0.0.1:9000"
ErrorLog /var/webs/wwwgreekgeo/log/error_log
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-agent}i\"" combined
CustomLog /var/webs/wwwgreekgeo/log/access_log combined
LogLevel debug
As you can see, I have made efforts to enable php debugging, but I still
can't see any php logging, in any php log:
/var/log/php-fpm/error.log
/var/log/php-fpm/www-error.log
The file: /var/webs/wwwgreekgeo/log/php_error_log remains empty
I've also followed these directions to enable Wordpress php logging:
https://codex.wordpress.org/WP_DEBUG but I didn't get any php logging
either.
Please advise: How can I enable full php logging and troubleshoot php on
this vhost?
Also: What would you advise, if possible, on the particular problem (php
processing hanging on this vhost only without any obvious reason)?
I've googled and tried many things for several hours, but I can't find a
solution.
Thanks in advance,
Nick
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] more recent perl version?
On 2/6/2017 2:05 μμ, hw wrote: That´s a good thing, though it can be difficult to run systems using ancient software. You may want to check the following paradigm (from another open source perl-based application) to create a Perl environment within your system, avoiding to tamper with it: https://metacpan.org/pod/App::Netdisco#Installation We are running it in production for years and has been great in maintenance and operation (despite my initial fears). Alternatively, you can use a container. See for example: https://linuxcontainers.org/ http://www.itzgeek.com/how-tos/linux/centos-how-tos/setup-linux-container-with-lxc-on-centos-7-rhel-7.html http://www.perlmonks.org/index.pl?node_id=1034720 Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 2/6/2017 10:58 πμ, Nikolaos Milas wrote: Have you checked if this bug/behavior has been reported or should we file a bug report? After a bit of search, I found the associated reports: https://bugs.centos.org/view.php?id=13351 https://bugzilla.redhat.com/show_bug.cgi?id=1454876 No solution yet, but -as a workaround- it seems that -at least- nfs problems are indeed solved with downgrading. Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NFS mount on Centos 7 crashing
On 2/6/2017 10:40 πμ, Philippe BOURDEU d'AGUERRE wrote: Reverting to rpcbind-0.2.0-38.el7 solves the problem for me Thank you very much Philippe, I notice that I have upgraded to rpcbind-0.2.0-38.el7_3.x86_64 on May 26. Have you checked if this bug/behavior has been reported or should we file a bug report? Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] NFS mount on Centos 7 crashing
Hello, We have a VM (under KVM - a VPS service by our ISP) running CentOS 7. On it we have 2 NFS mounts, one for backup and one as a live file system (where there are two user homes as well): --- # cat /etc/fstab /dev/mapper/centos-root / xfs defaults0 0 UUID=7a3ae70a-8ef3-463b-8f5b-be4e2e7be894 /boot xfs defaults0 0 /dev/mapper/centos-swap swapswap defaults0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 10.201.40.34:/data/col1/hesperia-mount /hesperiamount nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 --- This setup has been working fine for over a year, even under significant load, without issues. However, yesterday, the "live" NFS mount (/hesperiamount) has started crashing. When bootingeverything is fine, but very soonafter boot we noticed that we lose communication to the mount, although the remote storage system is accessible(without reporting any errors) and no network issues have occurred. We found that dmesg reports failures with call traces (2 examples): https://pastebin.com/GVSDbxFr https://pastebin.com/WujKQuHG This happens repeatedly/consistently (after several reboots) so we have been forced to replace the NFS mount with a local mount (on a new local virtual hard disk), to restore normal system operation. So the fstab has now become: --- # cat /etc/fstab /dev/mapper/centos-root /xfs defaults0 0 UUID=7a3ae70a-8ef3-463b-8f5b-be4e2e7be894 /boot xfs defaults0 0 /dev/mapper/centos-swap swap swap defaults0 0 /dev/mapper/vg2-lv1 /hesperiamount xfs defaults0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 # 10.201.40.34:/data/col1/hesperia-mount /hesperiamount nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 --- Note that when I later mounted manually the same NFS share on the same box (in order to copy data from it using rsync), it did not crash (but it only had reads and no writes in this scenario). The share was manually mounted with the following command: # mount -vv -o auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 -t nfs 10.201.40.34:/data/col1/hesperia-mount /hesperiamount2 Questions: * Is this a known issue/bug? * Have we possibly made any NFS misconfigurations (which however have not caused any errors for about a year now)? * What could we do to prevent the error from occurring again? Please advise. Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Urgent: Need to change the location of a directory tree
On 1/6/2017 9:52 μμ, Mauricio Tavares wrote: 1. Make sure both users are not logged in. 2. Create new mountpoints 3. Edit fstab to point to new mountpoints. 4. Edit /etc/passwd to refer to the new mountpoint for the two users 5. mount -a Would that do the trick for you? Thanks Mauricio, Actually, the process you describe is the same as the one I described, with the difference that we use the same mount point for the new location (after unmounting the nfs mount), so we don't need to edit /etc/passwd. I completed this procedure successfully. Thanks again, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Urgent: Need to change the location of a directory tree
On 1/6/2017 6:06 μμ, Nikolaos Milas wrote: ...then remove the mount from fstab and the initial mount point /scimount and finally rename /scimount2 to /scimount ? Correction: ...then remove the mount from fstab and the initial mount point /mynfsmount and finally rename /mynfsmount2 to /mynfsmount ? Sorry for the confusion. (I changed the directory names while editing the mail, but I failed to change them all.) Looking forward to your advice. Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Urgent: Need to change the location of a directory tree
Hi, I am running CentOS 7 (fully updated) on a VM. This has a mounted nfs share (via fstab) (which mounts a remote storage system) on which we have created the home directories of 2 users Here are the home directories: /mynfsmount | |--/user1 |--/user1 We want to move this whole branch from the mounted NFS share to the local disk. What is the way to do so? Would it be enough to create a "mirror" branch on the local disk, say: /mynfsmount2 | |--/user1 |--/user1 (which is no more an nfsmount, despite the name), then remove the mount from fstab and the initial mount point /scimount and finally rename /scimount2 to /scimount ? Does it sound OK? Will we need to modify any other system info so that the above homes work correctly at their new location? Thanks a lot, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 6/5/2017 12:09 μμ, Nikolaos Milas wrote: The VM booted fine after /etc/fstab update! I did another test, which was also successful. Below follows the output from the process (after booting in troubleshooting mode using the CentOS 7 media disk): 1) Continue 2) Read-only mount 3) Skip to shell 4) Quit (Reboot) Please make a selection from the above: 1 === === Rescue Mount Your system has been mounted under /mmt/sysimage. If you would like to make your system the root environment, run the command: chroot /mnt/sysimage Please press to get a shell. When finished, please exit from the shell and your system will reboot. sh-4.2# umount /dev/vda1 sh-4.2# xfs_admin -U restore /dev/vda1 Clearing log and setting UUID writing all SBs new UUID = b05227b2-7c86-4ccf-81ff-204a9a80f789 sh-4.2# mount /dev/vda1 /mmt/sysimage/boot sh-4.2# chroot /mnt/sysimage bash-4.2# grub2-install /dev/vda Installing for i386-pc platform. Installation finished. No error reported. bash-4.2# nano /etc/fstab bash-4.2# exit sh-4.2# Note also that after logging into the (finally bootable) OS, we should follow the directions: "Resetting and Reinstalling GRUB 2". https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html#sec-Resetting_and_Reinstalling_GRUB_2 Best regards, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 6/5/2017 12:20 πμ, Nikolaos Milas wrote: [Perhaps I should have manually edited /etc/fstab as well to enter the new UUID?] Yes, that was it! The VM booted fine after /etc/fstab update! Case closed. It was a tricky one! Thank you all for your feedback and kind assistance! Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 9:10 μμ, Marcelo Roccasalva wrote:
xfs_admin -U restore /dev/vdal
Bingo!
I had to unmount the boot partition (being in Troubleshooting mode), run
the above command, which provided a new UUID and at last the partition
was recognized as xfs. (I forgot to copy the output to paste here.)
I then mounted the boot partition again, chrooted, grub2-install'ed
successfully, exited and rebooted.
The VM started booting, seemingly well, but after some time it took me
to emergency mode. ("Give root password for maintenance or type Ctrl-D
to continue.")
I'll have to check that tomorrow... I need some sleep now (it's after
midnight over here - in Athens, Greece).
[Perhaps I should have manually edited /etc/fstab as well to enter the
new UUID?]
Anyway, that was a good progress! Thanks for your great cooperation.
I'll keep you updated.
Cheers,
Nick
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 8:34 μμ, Gianluca Cecchi wrote: Your /mnt/sysimage/boot is under tmpfs not real disk... Sorry, I am not an expert, but it does seem to NOT be under tmpfs: Filesystem Size Used Avail Use% Mounted on ... /dev/vdal497M 192M 306M 39% /mnt/sysimage/boot ... Why do you say that the boot partition is under tmpfs? Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 8:46 μμ, Nikolaos Milas wrote: If so, may it be that this fix has not been rolled out to CentOS repos yet? Note: Both the original (backed up) and the restored (clone) VM are up-to-date. No new updates available in the standard CentOS repos. Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 8:29 μμ, Nikolaos Milas wrote: I am very puzzled with "unknown filesystem". After more googling, I found this bug report with a very recent fix: https://bugzilla.redhat.com/show_bug.cgi?id=1399487 It seems to me that this may be relevant in our case. If so, may it be that this fix has not been rolled out to CentOS repos yet? What is your opinion and your advice/suggestion(s)? Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 3:45 μμ, Gianluca Cecchi wrote: BTW: see also this paragraph in the provided RH EL link: 24.7.3. Resetting and Reinstalling GRUB 2 But i think is not your problem Yes, I have done that, without change in behavior. Also, after changing partitions flag does your fdisk command reflect the change? Yes. Is the error during boot the same as the one provided in your first e-mail? Yes. One final thing. When I had to change boot settings, I made different steps in choot environment in respect of the indication inside the image you sent. Specifically Verify if your boot partition is already mounted under /mnt/sysimage/boot in your current environment Yes, it is: sh-4.2# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/live-rw 2.0G 1.1G 930M 54% / devtmpfs 979M0 979M0% /dev tmpfs 1001M 4.0K 1001M1% /dev/shm tmpfs 1001M 8.3M 993M1% /run tmpfs 1001M0 1001M0% /sys/fs/cgroup /dev/sr0 680M 680M 0 100% /run/install/repo tmpfs 1001M 300K 1001M1% /tmp /dev/mapper/centos-root 18G 1.5G16G9% /mnt/sysimage /dev/vdal497M 192M 306M 39% /mnt/sysimage/boot /tmpfs 1001M0 1001M0% /mnt/sysimage/dev/shm If it is mounted on another mount point in your live env go and umount it and run mount /dev/vda1 /mnt/sysimage/boot Didn't need to. then chroot /mnt/sysimage OK, I did so: sh-4.2# chroot /mnt/sysimage bash-4.2# when you are in chrooted environment, probably you don't have special files for vda and vda1 because they are dinamically created; verify with ls -l /dev/vda* It seems I do have such files: bash-4.2# ls -la /dev/vda* brw-rw.1 root disk 252, 0 May 5 16:49 vda brw-rw.1 root disk 252, 1 May 5 16:49 vdal brw-rw.1 root disk 252, 2 May 5 16:49 vda2 If this is the case, go and create them mknod -m 660 /dev/vda b 253 0 mknod -m 660 /dev/vda1 b 253 1 Didn't need to. at this point grub2-install /dev/vda and let see the output of the command and its exit code As usual: bash-4.2# grub2-install /dev/vda Installing for i386-pc platform. grub2-install: error: unknown filesystem. at this point exit chrooted environment (exit) umount /mnt/sysimage/boot reboot and see if anything changes Didn't do it, because grub2-install above failed, so nothing changed. I am very puzzled with "unknown filesystem". Thanks for your time and help! I am looking forward to reaching a solution! All the best, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 3:15 μμ, Gianluca Cecchi wrote: ... grub2-install /dev/vda ... Was this one of the command you already tried? Yes, I have tried that multiple times, both from Troubleshooting Mode (booting using CentOS 7 Installation CD) and from within the actual system (booted using super-grub2 disk). I always get (from troubleshooting mode): # grub2-install --root-directory=/mnt/sysimage/ /dev/vda Installing for i386-pc platform. grub2-install: error: unknown filesystem. or (from within the OS): # grub2-install /dev/vda Installing for i386-pc platform. grub2-install: error: unknown filesystem. How can I fix that? Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 1:57 μμ, Gianluca Cecchi wrote: what do you get when you boot the VM (I imagine with supergrub2 you described) and run this lspci lspci -kn Here you are: # lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 00:03.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon 00:04.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device # lspci -kn 00:00.0 0600: 8086:1237 (rev 02) Subsystem: 1af4:1100 00:01.0 0601: 8086:7000 Subsystem: 1af4:1100 00:01.1 0101: 8086:7010 Subsystem: 1af4:1100 Kernel driver in use: ata_piix Kernel modules: ata_piix, pata_acpi, ata_generic 00:01.2 0c03: 8086:7020 (rev 01) Subsystem: 1af4:1100 Kernel driver in use: uhci_hcd 00:01.3 0680: 8086:7113 (rev 03) Subsystem: 1af4:1100 Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:02.0 0300: 1013:00b8 Subsystem: 1af4:1100 Kernel driver in use: cirrus Kernel modules: cirrus 00:03.0 00ff: 1af4:1002 Subsystem: 1af4:0005 Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:04.0 0100: 1af4:1001 Subsystem: 1af4:0002 Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:05.0 0200: 1af4:1000 Subsystem: 1af4:0001 Kernel driver in use: virtio-pci Kernel modules: virtio_pci Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 1:42 μμ, Nikolaos Milas wrote: Hmm, it seems that the boot flag should be removed from /dev/vda2 partition? Actually, I tried this and left the boot flag only to /dev/vda1. I rebooted and I am still getting the same error. :-( I was hoping we were close to a solution... Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 1:19 μμ, Gianluca Cecchi wrote: Could you verify, if /dev/sda is your boot disk, with the command fdisk -l /dev/sda ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x942d1f03 Device BootStart End Blocks Id System dev/vdal * 2048 1026047 512000 83 Linux dev/vda2 * 1026048 41943039 20458496 8e Linux LVM Hmm, it seems that the boot flag should be removed from /dev/vda2 partition? (How we do that?) BTW: are you using virt-manager to configure/run your VMs? Or direct virsh commans or what? It's a hosted VPS service, and I have a virtual console to the VM. Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 5:11 πμ, Barry Brimer wrote: Are the correct volumes referenced in your /etc/default/grub file? Thanks Barry for your feedback. Here is the output: http://iweb.noa.gr/files/centos7/scratchvm-data-20170505-01.png What can you tell from that? Cheers, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 5/5/2017 2:22 πμ, Marcelo Roccasalva wrote: when you boot via supergrub2, you get this kernel version (uname -r)? every kernel has it own initramfs where some binaries, libraries, modules and configuration files get copied from the running VM, so you need to boot from a newly created initramfs (which you find in grub2.conf) [Note: I am working on a fresh restored/cloned installation and I have executed on it your previous command (dracut...).] As you can see here: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-00.png ...I can select the kernel with which I boot. I select the latest one (marked blue in the image), which is also the one for which I have run the initramfs rebuild command. This indeed is the kernel version reported by the OS. I am still trying to find out how to make the OS load at boot... Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 4/5/2017 5:56 μμ, Marcelo Roccasalva wrote:
dracut -f /boot/initramfs-.img
I did:
# dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img
3.10.0-514.10.2.el7.x86_64
and it ended without reporting any error. However, when I rebooted,
nothing changed ("no such device: . Entering rescue mode...").
Am I missing something?
Thanks,
Nick
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 4/5/2017 5:20 μμ, Marcelo Roccasalva wrote: Dumb question: the file starts with a dot, doesn't show up in "ls" without "-a". Of course, I check with ls -la.It is empty indeed. Even dumber question: the erroring UUID exist in the origin of thecloned guest? I guess you have rebuilt initramfs a few times now, so I believe it is irrelevant... Interestingly, I see in the origin VM, the same UUID as in the cloned guest. See below. I don't know anything about rebuilding initramfs; the whole restore process is automatic. (There is a manual method too, but I have not been successful with it either.) # blkid /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" TYPE="xfs" /dev/vda2: UUID="cey71w-b81q-w1se-0Cww-X2cr-Milx-dWw15Z" TYPE="LVM2_member" /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" TYPE="swap" # cat /etc/fstab /dev/mapper/centos-root / xfs defaults0 0 UUID=297e2939-d6f5-431a-9813-9848368ee306 /boot xfs defaults0 0 /dev/mapper/centos-swap swapswap defaults0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 Any ideas? Never used mondorestore to clone a VM, have you done it successfully before? I have always had success in all my (numerous) restores/clones with CentOS 5 and 6. I have not managed to have a fully successful (i.e. bootable) restore/clone of a CentOS 7 system yet (due to the above issue). Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 3/5/2017 5:24 μμ, Nikolaos Milas wrote: Using the supergrub2 disk I can boot and login successfully. Otherwise (i.e. directly) the box won't boot. In the meantime, I also tried rescatux (https://sourceforge.net/projects/rescatux/) repair disk; it failed as well. The situation remains the same. How can we fix this cloned CentOS 7 installation to become bootable? Please advise! Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 cloned VM cannot boot
On 3/5/2017 10:41 μμ, Marcelo Roccasalva wrote: Does the UUID of root filesystem in /etc/fstab match the actual UUID as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs" /dev/vda2: UUID="OR1eUA-1hhb-PCff-qybQ-rLt4-JuTN-EcWX61" TYPE="LVM2_member" /dev/sr0: UUID="2017-03-16-21-15-06-00" LABEL="ISOIMAGE" TYPE="iso9660" PTTYPE="PMBR" /dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" TYPE="xfs" /dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" TYPE="swap" # cat /etc/fstab # # /etc/fstab # Created by anaconda on Thu Dec 8 13:40:06 2016 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/centos-root / xfs defaults0 0 UUID=297e2939-d6f5-431a-9813-9848368ee306 /boot xfs defaults0 0 /dev/mapper/centos-swap swapswap defaults0 0 10.201.40.34:/data/col1/noc-bkups-1 /mnt/dd2500-1 nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0 Any other ideas? Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 7 cloned VM cannot boot
Hello, I'm struggling to make a cloned CentOS 7 VM (under KVM) to work. The VM was cloned using mondorestore. Restore appears successful but the VM won't boot; see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I booted with CentOS 7 disk in troubleshooting mode (where the virtual disk was automatically mounted without issues) and I tried to repair: http://iweb.noa.gr/files/centos7/el7-rescue-scratchvm-20170502-01.png Also: # grub2-mkconfig -o /boot/grub2/grub.cfg ... /usr/sbin/grub2-probe: error: unknown filesystem. I then tried to repair using: https://sourceforge.net/p/boot-repair-cd/home/Home/ but it didn't manage to solve the problem. (It reported success but the VM still won't boot.) More interesting was the effort with the supergrub2 disk: http://www.supergrubdisk.org/super-grub2-disk/ This managed to identify the available "boot methods" and allowed me to boot correctly. See screenshots: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-00.png http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-01.png http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-02.png Once I logged in, I checked /etc/fstab and /boot/grub2/grub.cfg but I didn't see any obvious problem. The are here as well: http://iweb.noa.gr/files/centos7/fstab http://iweb.noa.gr/files/centos7/grub.cfg However, I also followed these directions: https://www.techbrown.com/reinstall-grub2-boot-loader-centos-7-rhel-7.shtml to rebuild grub2.conf. The commands were completed successfully. Unfortunately, the OS still won't boot: same issue, see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I again tried to boot using the supergrub2 disk; this time the boot method detection produced the (slightly different) list you see in image: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-05.png Using the supergrub2 disk I can boot and login successfully. Otherwise (i.e. directly) the box won't boot. As I know little about grub2 (and low-level linux) to troubleshoot the issue, can you please help identify and correct the problem? Why the VM always refuses to boot? Which is the reported device (on image -04) that remains unrecognized? I looked into /boot/grub/grub2.cfg but I didn't see any such UUID there. Where may it be referenced to be used during the boot process? Note: I never have such issues when restoring (using mondorestore) CentOS 5 or CentOS 6 mondoarchive backups (even on dissimilar virtual hardware). Can you please help me identify the problem, based on the above info, and make the VM normally bootable? Many thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange (?) device.map in CentOS 7 VM installations
On 5/1/2017 11:04 πμ, Nikolaos Milas wrote: Can others please report the content of /boot/grub2/device.map on their CentOS 7 (physical or virtual) installations? Thank you all for your reports. Since it seems this is generally the case with CentOS 7, does anyone also have access to RHEL 7 installations to verify if this is the case with these installations as well? And can any tech geek please explain when/why do we have these "duplicates" and if they are intentional or not? Any feedback regarding this "issue" and its possible repercussions will be appreciated! Thanks a lot, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange (?) device.map in CentOS 7 VM installations
On 4/1/2017 7:37 μμ, Gordon Messmer wrote: I don't see that on VMs that I manage. Some of the physical machines that I manage do have duplicates in the device.map. Thank you Gordon for your feedback! Can others please report the content of /boot/grub2/device.map on their CentOS 7 (physical or virtual) installations? And can any tech geek please explain when why do we have these duplicates and if they are intentional or not? Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange (?) device.map in CentOS 7 VM installations
On 29/12/2016 11:24 πμ, Nikolaos Milas wrote: ...I have found that all my CentOS 7 installations (VMs under KVM) have the same /boot/grub2/device.map, which seemingly refers to two HDs, although the VMs in fact include only one (virtual) HD. ... This is NOT the case with my CentOS 5 and CentOS 6 VMs, which all have a "correct" device map, with a single (hda0) entry. Is the above behavior expected? If not, what should be the expected way of operation and what may be the cause of it? I am trying to understand where something may be going wrong, so please help. Hello, I never got a reply on this, so I repeat the question: Is it normal in CentOS 7 to have a device map with two entries esp. when the (physical or virtual) hardware has only one hd ? Is the following normal? /boot/grub2/device.map: # this device map was generated by anaconda (hd0) /dev/vda (hd1) /dev/vda Please advise! Thanks, Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Strange (?) device.map in CentOS 7 VM installations
Hello, After repeated failing efforts to restore CentOS 7 backups (taken using mondorescue software), I have found that all my CentOS 7 installations (VMs under KVM) have the same /boot/grub2/device.map, which seemingly refers to two HDs, although the VMs in fact include only one (virtual) HD. For example: /boot/grub2/device.map # this device map was generated by anaconda (hd0) /dev/vda (hd1) /dev/vda Here is the hardware of the VM: # parted -l Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/centos-swap: 2147MB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End SizeFile system Flags 1 0.00B 2147MB 2147MB linux-swap(v1) Model: Linux device-mapper (linear) (dm) Disk /dev/mapper/centos-root: 18.8GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End SizeFile system Flags 1 0.00B 18.8GB 18.8GB xfs Model: Virtio Block Device (virtblk) Disk /dev/vda: 21.5GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End SizeType File system Flags 1 1049kB 525MB 524MB primary xfs boot 2 525MB 21.5GB 20.9GB primary lvm This is NOT the case with my CentOS 5 and CentOS 6 VMs, which all have a "correct" device map, with a single (hda0) entry. Is the above behavior expected? If not, what should be the expected way of operation and what may be the cause of it? I am trying to understand where something may be going wrong, so please help. Many Thanks! Nick ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Backup PC or other solution
On 7/5/2015 5:01 μμ, Robert Nichols wrote: I use rdiff-backup, but I hesitate to recommend a tool that has been unsupported for over 6 years and does have quite a few bugs. I have had good experience with mondrescue (mondoarchive, mondorestore) for years. It's a free, active project. See: http://www.mondorescue.org/ We are backing-up about 20 production servers (using cron jobs) weekly. Bare-metal recovery has been successful as well as cloning. Their mailing list is helpful and polite. I has saved my neck many times during the last 5 years. Although I have no experience with mondorescue on Centos 7, I recommend it at least for the other versions. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forward http traffic
On 8/1/2014 8:28 μμ, Les Mikesell wrote: The concept doesn't even make sense for TCP connections where the stack requires acks and sequencing. Are you trying to bridge to a capture device or something? Thank you all for your enlightening feedback, which helped me better understand my situation. I can see that in fact I can do with a forward proxy (and not use iptables at all). The goal is to transfer data from a data capture device (which incorporates a web server) lying on a private subnet (without NAT) to various destinations. I now understand that forwarding identical traffic using iptables to such destinations (even if it was possible) would not be the right way. The device can be instructed to send data via http to whatever destinations via a local http forward proxy (which has a public IP address but can be accessed from the private subnet). Case closed. Thank you all again, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forward http traffic
On 7/1/2014 6:19 μμ, Antonio da Silva Martins Junior wrote: If you put it that way only xxx will receive packets, to balance betwin both of them you will need this: -A PREROUTING -s 10.250.250.0/24 -p tcp -m tcp --dport 8080 -j DNAT --to-destination xxx.xxx.xxx.xxx-yyy.yyy.yyy.yyy:80 Thank you, According to man iptables, this defines an inclusive *range*. Yet, I don't want a range, but two (or more) distinct ip addresses. How can this be done? Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forward http traffic
On 8/1/2014 11:54 πμ, Antonio da Silva Martins Junior wrote: Well, I had only used with a range. Maybe you can take a look on a software load-balancer, like haproxy, or use something like nginx. Then forward to the load-balancer instead to the servers. Thanks, Actually, I don't want load balancing; I want incoming http traffic (to port 8080) to be forwarded to *ALL* defined target IP addresses. ...But I still don't know if this is possible with iptables. I hope someone here can provide more info. I am not sure if haproxy or nginx can be used to simply forward all inbound traffic to a number of public IP Addresses (anywhere on the Internet) at the same time, as this is a very special scenario: it is different both fom a forward proxy and from a reverse proxy -with or without load-balancing- (which is usually implemented with such software). If, however, it is feasible, I would be interested to know which is the directive for this feature in the respective software (so I can investigate further). Best regards, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Forward http traffic
Hello, On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables): *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -s 10.10.10.0/24 -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -s 10.10.10.0/24 -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT Now, I want to forward all http traffic coming in from 10.250.250.0/24, at local port 8080, to 2 particular IP Addresses (port 80). Is it enough to prepend (to the above) the following: *nat :PREROUTING ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A PREROUTING -s 10.250.250.0/24 -p tcp --dport 8080 -j DNAT --to-destination xxx.xxx.xxx.xxx:80 -A PREROUTING -s 10.250.250.0/24 -p tcp --dport 8080 -j DNAT --to-destination yyy.yyy.yyy.yyy:80 COMMIT ...? Please advise! Thanks in advance, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] php 5.1 to 5.3
I am using webtatic on CentOS 5.x. I started using it some years back because as I can remember (vaguely) I had problems using php53 RPMs (can't remember details, however). Thanks for php 5.4 info - I haven't used it yet. I installed remi (php 5.5) on CentOS 6.x but, yes, it seems many apps don't like php 5.5. Regards, Nick On 4/10/2013 6:15 μμ, Reindl Harald wrote: remi has already PHP 5.4 - so i doubt you are using it regulary otherwise you would know that and yes there is a large difference between PHP 5.3 and 5.4 5.3 does not break sane applications 5.4 breaks*any* non-utf8 application by changed charset defaults ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] php 5.1 to 5.3
On 4/10/2013 5:36 μμ, Leon Fauster wrote: Am 04.10.2013 um 13:51 schrieb Nikos Gatsis - Qbit ngat...@qbit.gr: Hello list I'm managing a web server with centos-release-5-9.el5.centos.1. I have php-5.1.6-40.el5_9 right now and I'd like to update it to php53. I wander if its easy or complicated. If somebody have any instructions I'd be very glad! I am using http://rpms.famillecollet.com/ and http://www.webtatic.com/projects/yum-repository/ for a long time without issues. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] about backup of centos instead of fresh install
On 18/4/2013 5:11 μμ, m.r...@5-cent.us wrote: I*strongly* second that. In real, professional work environments, you've got developers, testers, and production, on*separate* boxes; if you're short on hardware and cash, a VM on the dev box is the way to go. To expand on this correct advice: You can use CloneZilla or mondorescue to clone your production system to a test VM; then experiment there as much you like. :-) N ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem building powerdns from EPEL
Hi, I just tried to build using http://dl.fedoraproject.org/pub/epel/6/SRPMS/pdns-3.1-2.el6.src.rpm on CentOS 6.4 final (kernel: 2.6.32-358.2.1.el6.x86_64), but it failed when looking for ldap libs: Note: I did not change anything in the original spec file. ... + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --sysconfdir=/etc/pdns --libdir=/usr/lib64/pdns --disable-static --with-modules= --with-lua '--with-dynmodules= gmysql gpgsql pipe geo ldap gsqlite3' --enable-cryptopp ... checking for ldap_set_option in -lldap_r... no checking for ldap_set_option in -lldap... no configure: error: ldap library (libldap) not found However, libldap exists at the required place (/usr/lib64): $ ls -la /usr/lib64/ | grep ldap drwxr-xr-x. 4 root root 4096 Mar 11 16:06 evolution-openldap lrwxrwxrwx. 1 root root 10 Sep 21 2012 libldap-2.4.so.2 - libldap.so -rw-r--r--1 root root 781914 Mar 20 15:57 libldapbackend.a -rwxr-xr-x1 root root 1151 Mar 20 15:57 libldapbackend.la -rwxr-xr-x1 root root 379419 Mar 20 15:57 libldapbackend.so lrwxrwxrwx. 1 root root 12 Sep 21 2012 libldap_r-2.4.so.2 - libldap_r.so lrwxrwxrwx1 root root 29 Mar 11 16:06 libldap_r.so - /lib64/libldap_r-2.4.so.2.5.6 lrwxrwxrwx1 root root 27 Mar 11 16:06 libldap.so - /lib64/libldap-2.4.so.2.5.6 -rwxr-xr-x1 root root40320 Feb 22 09:49 libsmbldap.so.0 Here is the relevant part from config.log: ... configure:17992: checking for ldap_set_option in -lldap_r configure:18017: g++ -o conftest -D_GNU_SOURCE -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DLDAP_DEPRECATED -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic conftest.cpp -lldap_r -lz 5 /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libldap_r.so: undefined reference to `ber_sockbuf_io_udp' collect2: ld returned 1 exit status ... configure:18033: checking for ldap_set_option in -lldap configure:18058: g++ -o conftest -D_GNU_SOURCE -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DLDAP_DEPRECATED -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic conftest.cpp -lldap -lz 5 /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libldap.so: undefined reference to `ber_sockbuf_io_udp' collect2: ld returned 1 exit status Am I doing something wrong? Why it can't find the ldap libraries? Please advise. Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem building powerdns from EPEL
On 9/4/2013 11:56 μμ, m.r...@5-cent.us wrote: Interesting. Is there another ldap option in the configure? I ask, since the above shows that the ldap_set_option is*not* set Thanks for the reply. I don't see anything: $ ./configure --help | grep -i ldap $ But, in any case, the problem seems to be that libldap library cannot be found: configure: error: ldap library (libldap) not found What may be causing this? Regards, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] posfix admin issue
On 21/3/2013 11:06 πμ, Austin Einter wrote: My question is why it is redirecting wrongly to domain/login.php. I would suggest you visit postfixadmin project forum and/or subscribe to their mailing list. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Installing SOGo on Centos 5
Hello, I was following directions at: http://www.sogo.nu/english/support/faq/article/how-to-install-sogo-and-sope-through-yum-1.html to install SOGo on CentOS 5.9 and, noticing that among the dependencies is memcached and rpmforge includes a much more recent version than EPEL, I preferred rpmforge and therefore I set a higher priority for rpmforge repo (see below). [Note: I guess I could have left out epel in the first place, because I saw that no package was used from there, yet I thought I should follow the directions at the above page, which claim that epel should be enabled, just in case.] So I did: # yum --enablerepo=rpmforge,epel,rpmforge-extras,sogo-rhel5 install sogo sogo-devel sogo-debuginfo where I have the following priorities set: [base] priority=1 enabled=1 [updates] priority=1 enabled=1 [addons] priority=1 enabled=1 [extras] priority=5 enabled=1 [centosplus] priority=6 gpgcheck=1 enabled=0 [contrib] priority=15 [rpmforge] priority = 2 enabled = 0 [rpmforge-extras] priority = 2 enabled = 0 [epel] priority=5 enabled=0 [sogo-rhel5] enabled=0 priority=3 but I got: ... perl-AnyEvent-5.340-1.el5.rfx.x86_64 from rpmforge-extras has depsolving problems -- Missing Dependency: perl(Net::SSLeay) = 1.33 is needed by package perl-AnyEvent-5.340-1.el5.rfx.x86_64 (rpmforge-extras) Error: Missing Dependency: perl(Net::SSLeay) = 1.33 is needed by package perl-AnyEvent-5.340-1.el5.rfx.x86_64 (rpmforge-extras) However, it seems an RPM is available at rpmforge-extras (and is 1.33): # yum --enablerepo=rpmforge,rpmforge-extras,rpmforge-testing info perl-Net-SSLeay ... Available Packages Name : perl-Net-SSLeay Arch : x86_64 Version: 1.36 Release: 1.el5.rfx Size : 334 k Repo : rpmforge-extras Summary: Net-SSLeay module for perl URL: http://search.cpan.org/dist/Net-SSLeay/ License: Artistic/GPL Description: Net-SSLeay module for perl. Why this package isn't being used during dep solving? Any ideas? Am I doing something wrong? Please advise. Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Java app not observing ACLs
Hello, I have inherited a Java app, available as a jar, which has been moved from an HPUX server as is. [This app simply downloads a data file from an ftp server, processes its data and creates graph files.] It works fine on a CentOS 5 x86_64 machine with: jre-7u9-linux-x64.rpm but I've noticed it does not respect Linux ACLs. When run by a user who has access to a directory (where the app creates a file) only via ACLs (and not by basic user/group permissions), then I get permission denied issues. I've googled for the problem but have not been able to find references. Is anyone aware of such behavior and can suggest a solution? Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 - which repos to use?
On 27/1/2013 5:11 μμ, Johnny Hughes wrote: Taking gtk2 as in our example here, if you wanted a new gtk2 in CentOS-5.9, then you would have to rebuild the following packages: A quick (?) question: What is the best way to view dependencies? 1. We can use yum deplist xxx.rpm to view dependencies of a particular installed package, but we would like to limit output to only *already installed* packages and not view all suitable ones. Also, we would like to view dependencies as a full rpm name and not as they are output by default (e.g. not glibc.x86_64 2.12-1.80.el6_3.6 but glibc-2.12-1.80.el6_3.6.x86_64) 2. Is there a way to find out the opposite, i.e. which *installed* packages are dependent on a particular installed package? In your example above (about gtk2), how could we have produced the list of dependent-on-it packages which you have kindly provided? Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 - which repos to use?
On 27/1/2013 5:11 μμ, Johnny Hughes wrote: So upgrading one package can cause a domino effect that means you have either broken a bunch of packages or you have to rebuild a bunch of packages. That is why you should *only* upgrade what is VITAL for your application(s), and in a carefully planned manner, as Johnny explains. Building on the example I gave earlier, OpenLDAP Server, which IS important to be current in production due to critical bug (not only security) fixes, can be safely upgraded using LTB project RPMs (http://ltb-project.org/wiki/) which allows a current version WITHOUT affecting the rest of the system (by using alternate paths to install libs, executables etc.). Any other Servers in need for a current version can be safely upgraded through a careful approach to make sure they don't break other things. So, get to know your OS, your apps, your (S)RPMs; then plan, test on a non-production system, then plan deployment in production. For example, we *only* upgrade other critical apps like Postfix, Dovecot etc. when running as enterprise servers. There is no other option here; for example, Postfix as available in RHEL/CentOS 5, is no more supported by the Postfix developer. We have to build our own RPMs based on our particular requirements. We enjoy the stability of CentOS because it allows us to only upgrade what is vital. We don't care about Gnome and other modernization(s). Our CentOS 5 enterprise servers do not even have Gnome installed. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 - which repos to use?
On 25/1/2013 11:28 μμ, Leon Fauster wrote: not the CentOS(-Team) but the user it self is risking this … True. CentOS/RHEL are using the least-risk policy by rarely updating packages, except for serious bug/security fixes and that helps provide peace of mind from the base OS. Yet, I have come to believe that Systems Administration is not trivial in terms of decision-making; in fact, one could say that it may be a highly philosophical (!) job. You must balance availability of features, stability, manageability, security, package dependencies, application/service deployment and maintenance and more. Experience, knowledge and a thoughtful attitude will hopefully help find a golden section between all these through time on a per case-basis. No systems are identical. The sysadmins have to *study* their environment and needs and then design the proper solution on each case. As a simple example, if there is a requirement to run OpenLDAP *as a server* on a CentOS OS, the sysadmin MUST find *how* to run the latest version (which is the only approved one for OpenLDAP server deployments by the OpenLDAP project). Deploying OpenLDAP using the packages available by either CentOS 5 or 6 repos is unacceptable. 2c, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 - which repos to use?
On 26/1/2013 7:42 πμ, Les Mikesell wrote: If you find a 100% reliable solution, please post it. I suggest very carefully selecting particular packages (and groups thereof) from whatever repos (or from individual experienced users' efforts), testing them thoroughly on test systems (usually a set of VMs) and/or building your own packages based on selected/modified SRPMs (according to your own requirements), then defining your own enterprise repo(s) for internal use. Why not use other distro(s) with more recent packages? Because I have tried them and I only find RHEL / CentOS a truly Enterprise System. At least it suits me. :-) There is no such thing as a 100% reliable system if you don't do things right. You can easily screw (in terms of security and reliability) your Vanilla RHEL/CentOS with one wrong setting, even using your safe repos. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Having trouble updating glibc on Centos 6.3
On 21/1/2013 7:14 μμ, Richard Reina wrote: However I need glibc-2.15 Read: https://www.redhat.com/archives/rhelv6-list/2012-August/msg00015.html Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] load balancer recommendations
On 19/1/2013 10:35 μμ, Boris Epstein wrote: Any advice on what may help us would be greatly appreciated. Have you checked HAProxy (http://haproxy.1wt.eu)? Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] load balancer recommendations
On 19/1/2013 10:35 μμ, Boris Epstein wrote: Any advice on what may help us would be greatly appreciated. Some reading that might help in making up your mind: http://www.chinanetcloud.com/blog/load-balancing-haproxy-vs-nginx http://www.techopsguys.com/tag/netscaler/ http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/ http://blog.exceliance.fr/2012/08/25/haproxy-varnish-and-the-single-hostname-website/ You'll undoubtedly find more material on the iNet, but I hope the above may serve as a starting point. Good luck, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Building Dovecot CentOS 5 RPMs with custom LDAP packages
On 11/1/2013 1:44 μμ, fakessh @ wrote:
I do not know the only thing I can tell you that laziness is a value in
the computer
You are partly right.
However, IMHO building dovecot using standard openldap-devel on CentOS 5
means that, even though the final RPM works, it will use *ancient*
openldap v2.3 libraries.
If we manage to use custom openldap libaries (like those from LTB
Openldap builds) then Dovecot can be built against modern/current
Openldap v2.4 libraries. That may provide significant improvements to
the final RPM, in terms of LDAP usage.
In any case, I found the solution (based on the documentation:
http://wiki2.dovecot.org/CompilingSource); I added the following lines
(marked below with ++) in your spec file:
%build
export PATH=/usr/kerberos/bin:$PATH
#required for fdpass.c line 125,190: dereferencing type-punned
pointer will break strict-aliasing rules
++ export CPPFLAGS=${CPPFLAGS} -I/usr/local/openldap/include
++ export LDFLAGS=${LDFLAGS} -L/usr/local/openldap/lib64
export CFLAGS=$RPM_OPT_FLAGS -fno-strict-aliasing
%configure
INSTALL_DATA=install -c -p -m644 \
--docdir=%{_docdir}/%{name}-%{version} \
--disable-static \
--disable-rpath \
--with-nss \
--with-shadow\
--with-pam \
--with-gssapi=plugin \
--with-ldap=plugin \
...
So, this produces a dovecot package based on Openldap 2.4
libraries(follows excerpt from the rpmbuild output):
...
Requires(interp): /bin/sh /bin/sh /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1
rpmlib(PayloadFilesHavePrefix) = 4.0-1
Requires(pre): /bin/sh shadow-utils
Requires(post): /bin/sh chkconfig shadow-utils
Requires(preun): /bin/sh chkconfig initscripts shadow-utils
Requires(postun): /bin/sh initscripts
Requires: /bin/bash /bin/sh config(dovecot) = 1:2.1.13-3.centme
initscripts ... libldap-2.4.so.2()(64bit) ...
...
It was initially using: libldap-2.3.so.0()(64bit)
Regards,
Nick
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Building Dovecot CentOS 5 RPMs with custom LDAP packages
On 12/1/2013 11:09 πμ, Nikolaos Milas wrote:
++ export LDFLAGS=${LDFLAGS} -L/usr/local/openldap/lib64
Or, more correctly:
export LDFLAGS=${LDFLAGS} -L/usr/local/openldap/lib64 -lldap
Nick
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Building Dovecot CentOS 5 RPMs with custom LDAP packages
On 20/4/2012 11:10 μμ, fakessh wrote:
look my personal rpm source of dovecot
its more simply and stable
http://ns.fakessh.eu/rpms/dovecot-2.1.4-1.centme.el5.src.rpm
Hi fakessh,
I was looking at your:
http://ns.fakessh.eu/rpms/dovecot-2.1.8-1.centme.src.rpm package (after
adapting to build for 2.1.13) and I am trying to figure out how to build
with custom LDAP libraries. I build Postfix using:
CCARGS=${CCARGS} -DHAS_LDAP -I/usr/local/openldap/include
AUXLIBS=${AUXLIBS} -L/usr/local/openldap/lib64 -lldap -llber
and:
BuildRequires: openldap-ltb-debuginfo = 2.4.33
Your Dovecot spec file (with respect to LDAP) only states:
BuildRequires: openldap-devel
So, I can change that to:
BuildRequires: openldap-ltb-debuginfo = 2.4.33
but I will need to define custom locations for the libraries. How do I
do that in your spec file?
Please advise. (Sorry, I am not an RPM-build guru.)
Thanks in advance.
Regards,
Nick
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] web mail and Squirrelmail
On 19/12/2012 9:43 πμ, M. Fioretti wrote: what about Sogo: Is it slower/more complicated to install... any comment is appreciated! I have not used SoGo yet, but I have read good things about it from many admins. It is probably the only one free/open-source solution which works well with Outlook sync and with Thunderbird/Lightning sync. I plan to try it out soon. Read this thread too: http://www.mail-archive.com/dovecot@dovecot.org/msg49002.html I have used Horde (in test mode, not in production) and it is good, but we had various issues, esp. when working with mobile devices. A bit complex in configuring / maintaining. We have also tested briefly FengOffice, which is slightly different: a groupware application, but it offers a web-based mail client with the ability to define multiple accounts. Other free groupware projects incorporating mail functionality: kolab, egroupware etc. We are currently still using SquirrelMail. I hate the GUI (aesthetically), but it works well and there are plugins for about everything one would ask. If only someone could create a nice contemporary GUI (HTML 5) for it! If someone wants Outlook / Thunderbird sync functionality, I would suggest starting from SoGo (even though I have not tested it yet). There are other open-source systems too which are not free: Zarafa, Zimbra, Open-Xchange etc. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOS: Production VM not starting!
On 11/12/2012 4:33 πμ, Markus Falb wrote: I had a look at your sreenshot. Output stops at the moment init is taking over. I suspect that console output is going elsewhere, maybe to a serial console. That way it could well be that the machine is doing something but you just can not see it. My first bet would have been a fsck Thanks, I think you are probably right. This VM features a large (virtual) data hard disk, and I found that it was mounted (in /etc/fstab) with autocheck options. Therefore, to avoid this problem in the future, I changed to 0 0 options. I had already suspected this (an auto fsck) might be the case, but in such cases in the past (with other VMs), the process was visible in the virtual console, while in this case apparently it was not. However, I did not find in /var/log/messages any instance of fsck checks during loading. Thanks again. Regards, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOS: Production VM not starting!
On 12/12/2012 7:37 πμ, Gordon Messmer wrote: On 12/10/2012 05:01 PM, Nikolaos Milas wrote: I still wonder what caused that delay. What does getenforce output? It sort of looks like you went from an SELinux-disabled configuration to an enforcing or permissive configuration and required a relabel. Thank you for helping find the cause of this behavior. SELinux was always disabled (and still is) on that VM: # getenforce Disabled Any other ideas would be appreciated. Regards, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOS: Production VM not starting!
On 12/12/2012 7:35 μμ, Markus Falb wrote: Sadly, boot.log on my CentOS 5 machines is empty and so will be yours. Yes, I had checked already, it's always 0 size... Thanks for your info. Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] SOS: Production VM not starting!
I am using a VM with CentOS 5.8 x86_64 under KVM. I only have console access to the VM through a virtual console (web based). Tonight, after a routine yum update, I did a shutdown -r now due to kernel update and the VM won't start. See console screenshot vm1.png: https://vmail.noa.gr/files/vm1.png There is an error (which I haven't seen before): type=1404 audit (...): selinux=0 auid=... ses= ... (see vm1.png above) (The system cannot load even with the old kernel; the same error occurs.) Note that SElinux is disabled on this system. I booted in rescue mode, and auto mount was unsuccessful (see https://vmail.noa.gr/files/vm2.png). The log of the rescue process shows some error (see https://vmail.noa.gr/files/vm4.png) However, later I successfully mounted it using: mount -t ext3 /dev/vda3 /mnt/sysimage I then did a umount and: fsck.ext3 /dev/vda3 which found it clean (see https://vmail.noa.gr/files/vm3.png). What is wrong there? Can you please guide me on how to make it work again? This is a production ftp machine. Please help to revive. Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOS: Production VM not starting!
On 11/12/2012 1:07 πμ, Eero Volotinen wrote: Is this really error? I Thanks for replying. Don't know, but it hangs there forever (at least it appears so - haven't waited more than half an hour, but it's already too much). maybe you need to disable selinux before trying to mount rescue environment? Hmm, selinux is already disabled. How can I adjust selinux settings in the rescue environment? How about installing new vm and just copying files and settings to it? I would like to avoid it, if possible. I would still need to somehow make this one visible on the network, to be able to copy large data files. My next bet would be to restore from backup, but I would rather make the current VM work. Can you boot this vm to single user mode ? No, it gets stuck at the same point as well. Any ideas why it keeps waiting forever at that point? Thanks, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SOS: Production VM not starting!
On 11/12/2012 1:24 πμ, Nikolaos Milas wrote: Any ideas why it keeps waiting forever at that point? After having left it alone for an hour or so, I found it had booted successfully. Didn't find anything serious in /var/log/messages. I still wonder what caused that delay. So, red alarm is over. Regards, NIck ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6.3 x86_64, drbd, which repo? atrpms or elrepo?
On 8/11/2012 12:59 μμ, Rafał Radecki wrote: Hi all. I am currently installing drbd on Centos 6.3 x86_64 and have two possible repos to choose. Which one in your opinion is better/provides more stable packages/etc.? IMHO, you will have no problems whatever you choose, but note that packages sometimes are built differently, so paths, various scripts, required libraries etc. may be different. If there are no such differences, I would choose the most recent version. If there are, it gets more complex; you might need to test (on a test environment) both, before setting up a production environment. Good luck, Nick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
