Re: [CentOS] SAMBA as AD DC
Why don't you use Sernet Enterprise Samba? They provide precompiled packages for a bunch of distros. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SAMBA as AD DC
On 09/14/2014 06:39 AM, Markus Steinborn wrote: Frantisek Hanzlik wrote: Are somewhere for these distribution available (unofficial) Samba4 RPMs packages with Heimdal Kerberos? I am trying to build some - as I want them, too. See http://rghost.net/57999078 for a xompressed tarball with the mock result (i. e. srpm, rpm and build logs). The package is working, but there is one problem I need help to fix it: Starting samba by "systemctl start samba.service" or "service start samba" seems to start samba, but if you try to join a domain from a windows client, it will fail reproting that the rpc server is not available. If you start samba by running "/usr/sbin/samba" from a console where root is logged in, samba is working as expected: Windows clients can join the domain. Any idea how to fix that issue? Would this be due to not starting the nmb service? Samba provide two services smb AND nmb, you want to ensure both are running. HTH Thanks + Greetings from Germany Markus Steinborn ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C5 : Deleting un-deletable files ?
Thank you to Steven and to Valeri for an excellent idea. The fsck cured the problem. The problem files were removed by fsck during its recovery/rectification. Thanks again. Paul. England, EU Good luck for Scotland's Independence ! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS on VPS File System in read-only mode
On Sat, Sep 13, 2014 at 06:46:40PM -0300, Pablo Parodi wrote: > Every saturday (I have installed this vps since 3 weeks ago) I check the > status of the server I found that the file system is in read-only mode The most common reason for this is a disk that is throwing errors. When this is the system disk, it inhibits logging the error in /var/log/messages. However, the error will be logged in other places. 3 places to check: 1) Run the 'dmesg' command, look for errors 1a) (If you had a remote syslog server configured, you won't miss errors in /var/log/messages because the system disk is read-only) 2) 'cat /dev/vcs' to see if there is anything on the console. (A server will ideally have a console log configured to not miss anything.) 3) 'smartctl -a /dev/sda' will show you if the disk has failed its self-test. (Ideally you have it configured to email you in this case.) > I suppose that the issue is a very high I/O request on the HD during the > backup process. I have never seen high I/O rates cause a read-only filesystem, except in the case where a disk error was visible. Linux has no problems with extremely busy disks; I have clusters with 100s of servers that run their disks with high I/O requests 24 hours a day for years, with no problems that were not visible in the logs 1-3. -- greg p.s. your English is pretty good! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ink
On 09/12/2014 08:23 PM, Valeri Galtsev wrote: On Fri, September 12, 2014 12:08 pm, m.r...@5-cent.us wrote: Frank Cox wrote: On Fri, 12 Sep 2014 12:52:53 -0400 Mauricio Tavares wrote: If it makes you feel any better, I found out a new cartridge for my home laser printer is $45 while the new version of my printer is $10 more. It's my understanding that the cartridges that come with new printers usually contain less ink or toner than the replacement cartridges do. They are called a "starter cartridge" to differentiate them from the replacement ones. They all do, toner and ink. Less is defined, by the way, as "half as much, literally, as the full replacement". Lets them diminish "apparent" cost of new printer, thus making their printer look less expensive and more competitive to what competitions have. After all they do the same... Also, the majority of buyers never look into technical part, just compare products using "pricegrabber" ;-) Which is the reality that doesn't do much good for the progress. I'm having in mind really good hardware which also lasts forever. (and still works when it is obsolete, which though sounds counter-productive) My wife still prefers the color rendering on our HP7310; all her letterheads are set up for it and print the 'wrong' color on the HP8500 and HP8600. The 8500 is still around as that is all I can print to from my corporate notebook, and only when I am off the vpn; so it is off most of the time. So we have 3 all-in-one printers that are used for different tasks. And none of them support T.38... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS on VPS File System in read-only mode
Hello All, First of all I want say thanks for all the info I see every time in this list. Second, sorry for my basic english. I writting this because I'm experiencing an issue with a Centos over a VPS. Every saturday (I have installed this vps since 3 weeks ago) I check the status of the server I found that the file system is in read-only mode #touch test touch: cannot touch `test': Read-only file system # mount -o remount / mount: block device /dev/sda1 is write-protected, mounting read-only Looking for info in the logs, I don't know how to get the root cause of the issue. But I can see that the last writing process is marked about the 1:40 hr #ls -ltr - /var/log -rw--- 1 root root 479825 Sep 13 01:20 maillog -rw--- 1 root root 229268 Sep 13 01:30 cron -rw--- 1 root root 106941 Sep 13 01:34 messages (now is Sep 13 18hr) The centos is mounted on a VPS. The VPS server is a Proxmox. The sysadmin of the VPS told me that there is a backup process running on friday at midnight. I suppose that the issue is a very high I/O request on the HD during the backup process. ( example in vmware http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306 ) # uname -a Linux 2.6.18-371.12.1.el5 #1 SMP Wed Sep 3 16:22:34 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux There is any kind of workarround for this (make the centos more flexible about the I/O timeouts or fails) Or maybe there is something to recommend to the VPS sysadmin to solve this issue? more info: # more /etc/fstab LABEL=/ / ext3defaults1 1 tmpfs /dev/shmtmpfs defaults0 0 devpts /dev/ptsdevpts gid=5,mode=620 0 0 sysfs /syssysfs defaults0 0 proc/proc procdefaults0 0 LABEL=SWAP-sda2 swapswapdefaults0 0 #df -h FilesystemSize Used Avail Use% Mounted on /dev/sda1 19G 3.4G 15G 19% / tmpfs 502M 0 502M 0% /dev/shm The previous times it happened the fsck after a reboot fixed the issue. Thanks in advance. PP ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wml / centos7
Am 13.09.2014 um 20:36 schrieb Reindl Harald: fine that you know what you mean "wml" can be a lot of different things that's why the www provides links so others know what you are talking about oops sorry, it's the website meta language ... http://thewml.org/ - an offline website generation engine and toolset which in pre-php times provided a nifty way of generating websites with many features like diversion, macro expansion, file inclusion, etc. Regards Michael PS: Ooops, sorry, first reply went to you personally ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wml / centos7
Am 13.09.2014 um 16:21 schrieb Michael Kress: Hi, anybody got wml running under centos7? Got problems either compiling it or finding an rpm. TIA for any hint! ... and BTW, the sw-wml mailing list is not available anymore :-( ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SAMBA as AD DC
Frantisek Hanzlik wrote: Are somewhere for these distribution available (unofficial) Samba4 RPMs packages with Heimdal Kerberos? I am trying to build some - as I want them, too. See http://rghost.net/57999078 for a xompressed tarball with the mock result (i. e. srpm, rpm and build logs). The package is working, but there is one problem I need help to fix it: Starting samba by "systemctl start samba.service" or "service start samba" seems to start samba, but if you try to join a domain from a windows client, it will fail reproting that the rpc server is not available. If you start samba by running "/usr/sbin/samba" from a console where root is logged in, samba is working as expected: Windows clients can join the domain. Any idea how to fix that issue? Thanks + Greetings from Germany Markus Steinborn ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C5 : Deleting un-deletable files ?
On Sat, 2014-09-13 at 12:37 -0500, Steven Stern wrote: > Have you run an fsck on this partition lately? Doing so now. -- Regards, Paul. England, EU. Centos, Exim, Apache, Libre Office is the future. Micro$oft is the past. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C5 : Deleting un-deletable files ?
After unmounting filesystem (assuming this is one of filesystems you can
not run fsck when it is mounted) and running fsck as Steven suggested, try
to delete files in question (if they are still present). If they still
resist, there may be immutable bit that got set somehow, you will need to
use chattr command then to unset it first, then you should be able to
delete files.
Good luck.
Valeri
On Sat, September 13, 2014 12:20 pm, Always Learning wrote:
>
> During a routine trawl through the ext3 files, I found some astronomical
> file sizes, billions and billions of GB.
> They also has strange user and group names.
> I can not delete these "weird files" (the term used by the operating
> system utilities).
>
> Here are a few examples. The original files were created on Windoze 98
> version 2 circa 2001.
>
>> 2411957 p--x---rwx 65487 299196551 2101198676775118685 Apr
>> 5 1943 2434.thm
>> 2411959 ?--xr-srwT 6581 42211 24637 1333254828 Jan
>> 30 2029 2435
>> 2411960 -rwxr-xr-x 44608 305922048 3679253821 14580319157523353423 Dec
>> 1 1949 2437
>
> lsattr: Operation not supported While reading flags on .
>
> stat ... A "normal" file looks this this example:
>
>> File: `2436'
>> Size: 47537 Blocks: 96 IO Block: 4096 regular file
>> Device: fd00h/64768dInode: 2411956 Links: 1
>> Access: (0755/-rwxr-xr-x) Uid: (0/root) Gid: (0/root)
>> Access: 2014-09-13 17:36:21.0 +0100
>> Modify: 2001-02-21 00:52:50.0 +
>> Change: 2013-03-12 06:26:36.0 +
>
> The problem files look like this:
>
>> File: `2434.thm'
>> Size: 775118685 Blocks: 3429617551 IO Block: 4096 fifo
>> Device: fd00h/64768dInode: 2411957 Links: 65487
>> Access: (0107/p--x---rwx) Uid: (299196551/ UNKNOWN) Gid: (2101198676/
>> UNKNOWN)
>> Access: 1951-12-14 00:29:38.0 +
>> Modify: 1943-04-05 10:37:22.0 +0200
>> Change: 2011-08-13 06:50:44.0 +0100
>
>> File: `2435'
>> Size: 1333254828 Blocks: 1402834881 IO Block: 4096 weird file
>> Device: fd00h/64768dInode: 2411959 Links: 6581
>> Access: (3156/?--xr-srwT) Uid: (42211/ UNKNOWN) Gid: (24637/ UNKNOWN)
>> Access: 1926-11-04 02:28:28.0 +
>> Modify: 2029-01-30 15:25:30.0 +
>> Change: 1928-09-14 11:19:14.0 +0100
>
>> File: `2437'
>> Size: 14580319157523353423Blocks: 1664918158 IO Block: 4096
>> regular file
>> Device: fd00h/64768dInode: 2411960 Links: 44608
>> Access: (0755/-rwxr-xr-x) Uid: (305922048/ UNKNOWN) Gid: (3679253821/
>> UNKNOWN)
>> Access: 2014-09-13 17:36:28.0 +0100
>> Modify: 1949-12-01 22:31:41.0 +
>> Change: 2030-03-17 01:15:08.0 +
>
>
> rm: cannot remove `2437': Operation not permitted
>
> However using 'lsattr 2437' to expose the flags, then removing
> the flags with 'chattr -{flag) 2437' eventually permitted me to delete
> the file with 'rm 2437'.
>
> The remaining two files appear un-touchable.
>
> lsattr 2435
> lsattr: Operation not supported While reading flags on 2435
>
> chattr -a 2434.thm ('a' was a random choice)
> chattr: Operation not supported while reading flags on 2434.thm
>
> find . -inum 2411959 -exec rm -i {} \;
> rm: remove weird file `./2435'? y
> rm: cannot remove `./2435': Operation not permitted
>
> All advice, except to transfer everything to a new partition then reformat
> the bad partition (which I will do eventually), appreciated.
>
>
>
> --
> Thank you,
>
> Paul.
> England, EU.
>
>Centos, Exim, Apache, Libre Office is the future. Micro$oft is the
> past.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C5 : Deleting un-deletable files ?
On 09/13/2014 12:20 PM, Always Learning wrote:
>
> During a routine trawl through the ext3 files, I found some astronomical file
> sizes, billions and billions of GB.
> They also has strange user and group names.
> I can not delete these "weird files" (the term used by the operating system
> utilities).
>
> Here are a few examples. The original files were created on Windoze 98
> version 2 circa 2001.
>
>> 2411957 p--x---rwx 65487 299196551 2101198676775118685 Apr 5
>> 1943 2434.thm
>> 2411959 ?--xr-srwT 6581 42211 24637 1333254828 Jan 30
>> 2029 2435
>> 2411960 -rwxr-xr-x 44608 305922048 3679253821 14580319157523353423 Dec 1
>> 1949 2437
>
> lsattr: Operation not supported While reading flags on .
>
> stat ... A "normal" file looks this this example:
>
>> File: `2436'
>> Size: 47537 Blocks: 96 IO Block: 4096 regular file
>> Device: fd00h/64768dInode: 2411956 Links: 1
>> Access: (0755/-rwxr-xr-x) Uid: (0/root) Gid: (0/root)
>> Access: 2014-09-13 17:36:21.0 +0100
>> Modify: 2001-02-21 00:52:50.0 +
>> Change: 2013-03-12 06:26:36.0 +
>
> The problem files look like this:
>
>> File: `2434.thm'
>> Size: 775118685 Blocks: 3429617551 IO Block: 4096 fifo
>> Device: fd00h/64768dInode: 2411957 Links: 65487
>> Access: (0107/p--x---rwx) Uid: (299196551/ UNKNOWN) Gid: (2101198676/
>> UNKNOWN)
>> Access: 1951-12-14 00:29:38.0 +
>> Modify: 1943-04-05 10:37:22.0 +0200
>> Change: 2011-08-13 06:50:44.0 +0100
>
>> File: `2435'
>> Size: 1333254828 Blocks: 1402834881 IO Block: 4096 weird file
>> Device: fd00h/64768dInode: 2411959 Links: 6581
>> Access: (3156/?--xr-srwT) Uid: (42211/ UNKNOWN) Gid: (24637/ UNKNOWN)
>> Access: 1926-11-04 02:28:28.0 +
>> Modify: 2029-01-30 15:25:30.0 +
>> Change: 1928-09-14 11:19:14.0 +0100
>
>> File: `2437'
>> Size: 14580319157523353423Blocks: 1664918158 IO Block: 4096 regular
>> file
>> Device: fd00h/64768dInode: 2411960 Links: 44608
>> Access: (0755/-rwxr-xr-x) Uid: (305922048/ UNKNOWN) Gid: (3679253821/
>> UNKNOWN)
>> Access: 2014-09-13 17:36:28.0 +0100
>> Modify: 1949-12-01 22:31:41.0 +
>> Change: 2030-03-17 01:15:08.0 +
>
>
> rm: cannot remove `2437': Operation not permitted
>
> However using 'lsattr 2437' to expose the flags, then removing
> the flags with 'chattr -{flag) 2437' eventually permitted me to delete
> the file with 'rm 2437'.
>
> The remaining two files appear un-touchable.
>
> lsattr 2435
> lsattr: Operation not supported While reading flags on 2435
>
> chattr -a 2434.thm ('a' was a random choice)
> chattr: Operation not supported while reading flags on 2434.thm
>
> find . -inum 2411959 -exec rm -i {} \;
> rm: remove weird file `./2435'? y
> rm: cannot remove `./2435': Operation not permitted
>
> All advice, except to transfer everything to a new partition then reformat
> the bad partition (which I will do eventually), appreciated.
>
>
>
Have you run an fsck on this partition lately?
--
-- Steve
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] C5 : Deleting un-deletable files ?
During a routine trawl through the ext3 files, I found some astronomical file
sizes, billions and billions of GB.
They also has strange user and group names.
I can not delete these "weird files" (the term used by the operating system
utilities).
Here are a few examples. The original files were created on Windoze 98 version
2 circa 2001.
> 2411957 p--x---rwx 65487 299196551 2101198676775118685 Apr 5
> 1943 2434.thm
> 2411959 ?--xr-srwT 6581 42211 24637 1333254828 Jan 30
> 2029 2435
> 2411960 -rwxr-xr-x 44608 305922048 3679253821 14580319157523353423 Dec 1
> 1949 2437
lsattr: Operation not supported While reading flags on .
stat ... A "normal" file looks this this example:
> File: `2436'
> Size: 47537 Blocks: 96 IO Block: 4096 regular file
> Device: fd00h/64768dInode: 2411956 Links: 1
> Access: (0755/-rwxr-xr-x) Uid: (0/root) Gid: (0/root)
> Access: 2014-09-13 17:36:21.0 +0100
> Modify: 2001-02-21 00:52:50.0 +
> Change: 2013-03-12 06:26:36.0 +
The problem files look like this:
> File: `2434.thm'
> Size: 775118685 Blocks: 3429617551 IO Block: 4096 fifo
> Device: fd00h/64768dInode: 2411957 Links: 65487
> Access: (0107/p--x---rwx) Uid: (299196551/ UNKNOWN) Gid: (2101198676/
> UNKNOWN)
> Access: 1951-12-14 00:29:38.0 +
> Modify: 1943-04-05 10:37:22.0 +0200
> Change: 2011-08-13 06:50:44.0 +0100
> File: `2435'
> Size: 1333254828 Blocks: 1402834881 IO Block: 4096 weird file
> Device: fd00h/64768dInode: 2411959 Links: 6581
> Access: (3156/?--xr-srwT) Uid: (42211/ UNKNOWN) Gid: (24637/ UNKNOWN)
> Access: 1926-11-04 02:28:28.0 +
> Modify: 2029-01-30 15:25:30.0 +
> Change: 1928-09-14 11:19:14.0 +0100
> File: `2437'
> Size: 14580319157523353423Blocks: 1664918158 IO Block: 4096 regular
> file
> Device: fd00h/64768dInode: 2411960 Links: 44608
> Access: (0755/-rwxr-xr-x) Uid: (305922048/ UNKNOWN) Gid: (3679253821/
> UNKNOWN)
> Access: 2014-09-13 17:36:28.0 +0100
> Modify: 1949-12-01 22:31:41.0 +
> Change: 2030-03-17 01:15:08.0 +
rm: cannot remove `2437': Operation not permitted
However using 'lsattr 2437' to expose the flags, then removing
the flags with 'chattr -{flag) 2437' eventually permitted me to delete the
file with 'rm 2437'.
The remaining two files appear un-touchable.
lsattr 2435
lsattr: Operation not supported While reading flags on 2435
chattr -a 2434.thm ('a' was a random choice)
chattr: Operation not supported while reading flags on 2434.thm
find . -inum 2411959 -exec rm -i {} \;
rm: remove weird file `./2435'? y
rm: cannot remove `./2435': Operation not permitted
All advice, except to transfer everything to a new partition then reformat the
bad partition (which I will do eventually), appreciated.
--
Thank you,
Paul.
England, EU.
Centos, Exim, Apache, Libre Office is the future. Micro$oft is the past.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] wml / centos7
Hi, anybody got wml running under centos7? Got problems either compiling it or finding an rpm. TIA for any hint! Regards Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
