On Sun, May 21, 2017 at 12:51:50PM -0700, Gordon Messmer wrote:
> The bug report mentioned in the message you replied to indicates that the
> problem was fixed in samba's master branch with this commit:
>
> https://git.samba.org/?p=samba.git;a=commit;h=4d5680e9ae531c6dc4d0a6687abe6293b5d4f4f2
>
On 05/20/2017 06:10 PM, Adam Tauno Williams wrote:
Six months later, now on CentOS6.9, we still see the same issue -
constantly logging this message. Server packages are all up-to-date.
I find multiple reports on the Internet - but no solutions.
The bug report mentioned in the message you
On Wed, 2016-09-14 at 16:50 +0100, isdtor wrote:
> > Not sure what would cause that error message, nor have I
> > experienced it. Looks like other people have seen it:
> > https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+wi
> >
On Mon, 2017-03-20 at 04:53 +, Chris Murphy wrote:
> On Tue, Mar 14, 2017, 7:41 AM James B. Byrne wrote:
>
> > On Fri, March 10, 2017 11:57, m.r...@5-cent.us wrote:
> >
> > >
> > > Looks like only one sector's bad. Running badblocks should,
> > >
> You'll need to
On Tue, Mar 14, 2017, 7:41 AM James B. Byrne wrote:
> On Fri, March 10, 2017 11:57, m.r...@5-cent.us wrote:
>
> >
> > Looks like only one sector's bad. Running badblocks should,
> > I think, mark that sector as bad, so the system doesn't try
> > to read or write there.
On 03/18/2017 10:46 AM, James B. Byrne wrote:
When I try to run fsck on any of them I see the following error:
fsck from util-linux-ng.2.17.2
e2fsck 1.41.12.(17-May-2010)
fsck.ext2: No such file or directory while trying to open /dev/vg. . .
Once you've completed enabling the logical
I have a CentOS-6.8 system which has a suspected HHD failure. I have
booted it into rescue mode from a CentOS-6.5 minimal install CD in
order to run fsck -c on it. The system hosts several vms. I have
activated the lvs associated with these vm using pvscan -s ; vgscan ;
vgchange -ay. An lvscan
On Fri, March 10, 2017 11:57, m.r...@5-cent.us wrote:
>
> Looks like only one sector's bad. Running badblocks should,
> I think, mark that sector as bad, so the system doesn't try
> to read or write there. I've got a user whose workstation has
> had a bad sector running for over a year. However,
Talk about missing the email I wanted to reply too. Disregard...
>> On Mar 10, 2017, at 9:28 AM, Valeri Galtsev
>> wrote:
>>>
>>>
>>> On Fri, March 10, 2017 9:52 am, Warren Young wrote:
On Mar 10, 2017, at 6:32 AM, James B. Byrne wrote:
I get up around 0630, u can come anytime after that. I want to hit the range
that morning but if I
KNEW when you are arriving, I could plan around that...
> On Mar 10, 2017, at 9:28 AM, Valeri Galtsev wrote:
>>
>>
>> On Fri, March 10, 2017 9:52 am, Warren Young wrote:
On Mar 10, 2017, at 9:28 AM, Valeri Galtsev wrote:
>
>
> On Fri, March 10, 2017 9:52 am, Warren Young wrote:
>> On Mar 10, 2017, at 6:32 AM, James B. Byrne wrote:
>>>
>>> On Thu, March 9, 2017 09:46, John Hodrien wrote:
fsck's not
On Fri, March 10, 2017 9:52 am, Warren Young wrote:
> On Mar 10, 2017, at 6:32 AM, James B. Byrne wrote:
>>
>> On Thu, March 9, 2017 09:46, John Hodrien wrote:
>>>
>>> fsck's not good at finding disk errors, it finds filesystem errors.
>>
>> If not fsck then what?
>
>
James B. Byrne wrote:
>
> On Thu, March 9, 2017 09:46, John Hodrien wrote:
>> On Thu, 9 Mar 2017, James B. Byrne wrote:
>>
>>> This indicated that a bad sector on the underlying disk system might
>>> be the source of the problem. The guests were all shutdown, a
>>> /forcefsck file was created on
On Mar 10, 2017, at 6:32 AM, James B. Byrne wrote:
>
> On Thu, March 9, 2017 09:46, John Hodrien wrote:
>>
>> fsck's not good at finding disk errors, it finds filesystem errors.
>
> If not fsck then what?
badblocks(8).
___
On Thu, March 9, 2017 09:46, John Hodrien wrote:
> On Thu, 9 Mar 2017, James B. Byrne wrote:
>
>> This indicated that a bad sector on the underlying disk system might
>> be the source of the problem. The guests were all shutdown, a
>> /forcefsck file was created on the host system, and the host
On Thu, 9 Mar 2017, James B. Byrne wrote:
This indicated that a bad sector on the underlying disk system might
be the source of the problem. The guests were all shutdown, a
/forcefsck file was created on the host system, and the host system
remotely restarted.
fsck's not good at finding disk
We have a remote warm standby system running CentOS-6.8 as a KVM
system with multiple guests. One of the guests began reporting an
error when running aide.
Caught SIGBUS/SEGV while mmapping. File was truncated while aide was
running?
Caught SIGBUS/SEGV. Exiting
The /var/log/messages file
well it's simple really
the ssh-copy-id routine does not copy [in my case] the client
/root/.ssh/id_rsa.pub to the server
man says thats the default but that's not what is happening.
whatever it copies allows me to run a shell script from a console
without passwords but not from cron
hmmm
> has something changed in cron?
> has there been an update?
> Have looked in all the usual places.
>
> any help/suggestions?
The environment maybe, enable debug output on the job and redirect
or make sure the output is logged or picked up and mailed to you.
More than likely the ssh config that
I have a file on a Centos 6.8 server that I want to download to another
Centos 6.8 box in a remote location.
rsync used to work fine from within a shell script run by cron using ssh
and having set up passwordless login on each machine
the script runs fine from the command line, but not when
I have begun to see these messages in my morning reports:
WARNING: Kernel Errors Present
pciehp :00:1c.0:pcie04: Link Training Error occurs ...: 146
Time(s)
pciehp 0ng Error occurs ...: 1 Time(s)
pcieport :00:1c.0: bridge window [mem 0xd0a00.0 failed
with error -22
On 09/20/2016 04:03 PM, Robert Heller wrote:
> I have a server that is also a firewall router at a public library with
> a fiber optic Internet connection. It is running kernel
> 2.6.32-642.4.2.el6.x86_64 (current CentOS 6.8) and Iptables 1.4.7
> (current stock CentOS 6.8). I having trouble
I have a server that is also a firewall router at a public library with a
fiber optic Internet connection. It is running kernel
2.6.32-642.4.2.el6.x86_64 (current CentOS 6.8) and Iptables 1.4.7 (current
stock CentOS 6.8). I having trouble with Internet throughput. I am supposed to
be getting
Am 14.09.2016 um 17:50 schrieb isdtor :
>
>> Not sure what would cause that error message, nor have I experienced it.
>> Looks like other people have seen it:
>>
> Not sure what would cause that error message, nor have I experienced it.
> Looks like other people have seen it:
> https://www.google.com/?gws_rd=ssl#q=gss_init_sec_context+failed+with+%5BUnspecified+GSS+failure.++Minor+code+may+provide+more+information:+No+credentials+cache+found
I found no
> > net ads keytab create -U username
> > 8. Verify the contents of the Kerberos keytab file:
> > klist -ke
>
> This is a step I was missing. What is the purpose of the keytab? Can it help
> with the default ticket FILE:/tmp/krb5cc_0 expiration?
A Kerberos keytab contains Kerberos principals and
> You might want to take a look at "Integrating Red Hat Enterprise Linux 6 with
> Active Directory". It's the best document I've seen on this topic. I found
> that Samba/Kerberos/Winbind is the most complete solution for attaching a
> Samba fileserver in my AD environment.
>
> I have another samba server and upgraded it to samba4. testparm returns
> clean with the old config (ROLE_DOMAIN_PDC) and starts up fine. smbclient
> seems to work fine.
>
> The next thing now is to try and make it a domain member so it can auth
> against AD.
>
> Thanks, Andrew, I appreciate
I have another samba server and upgraded it to samba4. testparm returns clean
with the old config (ROLE_DOMAIN_PDC) and starts up fine. smbclient seems to
work fine.
The next thing now is to try and make it a domain member so it can auth against
AD.
Thanks, Andrew, I appreciate the pointers.
> Samba 4.x is an intimidating piece of software. If it can perfrom the same
> function and use the same config, I'm willing to try it.
Without log messages or process table info, it's hard to advise any further.
Generally speaking, Samba4 can do everything that Samba 3.6 does. If your
server
> 1. What is your output of testparm?
No errors or warnings, apart from
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
> 2. If you run top, are any Samba related processes (winbindd, smbd, etc)
> consuming excessively high amounts of CPU?
I did not observe this,
> Other than the original 6.8 release version 3.6.23-33, samba has not been
> functioning correctly for me under 6.8.
>
> The symptoms are that about 6-7 days after starting the server, users start
> complaining that they can no longer open documents on their share. Upon
> inspection, I find
Other than the original 6.8 release version 3.6.23-33, samba has not been
functioning correctly for me under 6.8.
The symptoms are that about 6-7 days after starting the server, users start
complaining that they can no longer open documents on their share. Upon
inspection, I find several,
greetings one and all.
when attempting to install centos 6.8 to an i386 mid tower, during
setup of hard disk partitions, selection is for /dev/sde.
if continued, after reboot, error is displayed after 'welcome to centos'.
lines read:
Checking filesystem
fsck.ext4: no such file or directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
wwp kirjoitti 3.8.2016 12:36:
> Hello Jari,
>
>
> On Tue, 02 Aug 2016 23:15:21 +0300 Jari Fredriksson wrote:
>
>> OK. I fixed this case just by dismounting the share before hibernate,
>> but I'll leave this here anyway. Just a
Hello Jari,
On Tue, 02 Aug 2016 23:15:21 +0300 Jari Fredriksson wrote:
> OK. I fixed this case just by dismounting the share before hibernate,
> but I'll leave this here anyway. Just a historic note or something ;)
I think this is a very common issue: cifs vs hibernation, it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK. I fixed this case just by dismounting the share before hibernate,
but I'll leave this here anyway. Just a historic note or something ;)
- --
ja...@iki.fi
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now, this is not apparently very common to CentOS or EL server, but I
need to hibernate one of myservers after a batch job daily. Current
kernel appears to fail with pm-hibernate now.
$ cat /etc/redhat-release
CentOS release 6.8 (Final)
$ uname -a
Hi,
I am also using CentOS 6.8 but it was a pristine installation on my side,
in
my case everything is working fine.
You may be facing this issue due to upgrade.
--Regards
Ashishkumar S. Yadav
On Wed, Jun 8, 2016 at 11:38 PM, Gilbert Sebenste <
seben...@weather.admin.niu.edu> wrote:
> Hello
Hello everyone,
Since I upgraded to CentOS 6.8 last week, I am having an issue whereby I
log out, and then it attempts to log me in as the same user. I then click
on another user and try to log in, but it instantly blows me right out
and back to the login prompt for the original user. I do have
On Tue, 2016-05-31 at 14:41 -0500, Johnny Hughes wrote:
> https://pgp.mit.edu/pks/lookup?op=get=0x4CA90C826AC163B3
>
> (my public key)
Thanks.
--
Regards,
Paul.
England, EU. England's place is in the European Union.
___
CentOS mailing list
On 05/31/2016 12:44 PM, Always Learning wrote:
>
> On Tue, 2016-05-31 at 15:04 +0100, isdtor wrote:
>
>> (Btw., Johnny, your signatures haven't verified in months. Don't know if the
>> list server is the problem or our corp mail server).
>
> On mine I get "Signature exists, but need public
On Tue, 2016-05-31 at 15:04 +0100, isdtor wrote:
> (Btw., Johnny, your signatures haven't verified in months. Don't know if the
> list server is the problem or our corp mail server).
On mine I get "Signature exists, but need public key"
--
Regards,
Paul.
England, EU. England's place
> > Yet, it is strange that it all worked under 6.7 and before.
>
> You've got the 3rd-party nvidia packages installed. Do you know which
> repo you got them from?
elrepo. I thought I had mentioned that somewhere.
___
CentOS mailing list
On Tue, May 31, 2016 at 03:04:56PM +0100, isdtor wrote:
> # ldd `which glxinfo` |grep nvidia
> libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x7f6de0558000)
> libnvidia-tls.so.346.35 =>
> /usr/lib64/nvidia/tls/libnvidia-tls.so.346.35 (0x7f6de0352000)
>
> (Btw., Johnny, your signatures haven't verified in months. Don't know if the
> list server is the problem or our corp mail server).
Must be our mail server ... sorry for the false alert.
___
CentOS mailing list
CentOS@centos.org
(Btw., Johnny, your signatures haven't verified in months. Don't know if the
list server is the problem or our corp mail server).
> [johnny@localhost ~]$ glxgears
> 1054 frames in 5.0 seconds = 210.750 FPS
> 1064 frames in 5.0 seconds = 212.735 FPS
> 1077 frames in 5.0 seconds = 215.366 FPS
>
On Sun, 2016-05-29 at 17:33 +0100, Always Learning wrote:
> RedirectMatch 301 ^(.*)$ http://new.domain.com/$1
should be:-
RedirectMatch 301 ^/(.*)$ http://new.domain.com/$1
--
Regards,
Paul.
England, EU. England's place is in the European
On Sat, 2016-05-28 at 13:03 -0600, Paul R. Ganci wrote:
..
How about
RewriteEngine on
RewriteCond %{REQUEST_URI} !^/test/ [NC]
RewriteCond %{REQUEST_URI} !^/my-folder/[NC]
RewriteRule ^(.*)$ http://www.newdomain.com/$1 [R=301,L]
or
On 05/28/2016 02:26 PM, Alexander Dalloz wrote:
May I suggest you enable special logging for the mod_rewrite activity?
https://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritelog
https://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriteloglevel
Yes this is a good idea.
--
Paul
Am 28.05.2016 um 22:08 schrieb Paul R. Ganci:
On 05/28/2016 01:35 PM, Alexander Dalloz wrote:
Am 28.05.2016 um 21:03 schrieb Paul R. Ganci:
Starting httpd: Syntax error on line 31 of
/etc/httpd/conf.d/olddomain.conf:
RewriteCond: bad argument line '%{REQUEST_URI}!^/test/
You missed a
On 05/28/2016 01:35 PM, Alexander Dalloz wrote:
Am 28.05.2016 um 21:03 schrieb Paul R. Ganci:
Starting httpd: Syntax error on line 31 of
/etc/httpd/conf.d/olddomain.conf:
RewriteCond: bad argument line '%{REQUEST_URI}!^/test/
You missed a whitespace between the server variable %{REUQEST_URI}
Am 28.05.2016 um 21:03 schrieb Paul R. Ganci:
I was wondering if somebody could help me with an Apache re-write rule.
Apparently CentOS 6.8 is running apache-2.2.15-53. I am trying
to redirect all pages except for two pages. The apache rewrite
directives in the httpd config are:
RewriteEngine
On 28.05.2016 21:03, Paul R. Ganci wrote:
I was wondering if somebody could help me with an Apache re-write
rule. Apparently CentOS 6.8 is running apache-2.2.15-53. I am trying
to redirect all pages except for two pages. The apache rewrite
directives in the httpd config are:
RewriteEngine on
I was wondering if somebody could help me with an Apache re-write rule.
Apparently CentOS 6.8 is running apache-2.2.15-53. I am trying
to redirect all pages except for two pages. The apache rewrite directives in
the httpd config are:
RewriteEngine on
RewriteCond %{REQUEST_URI}!^/test/
55 matches
Mail list logo