Re: [CentOS] [off list] Re: please block user

[g]

On 08/28/15 20:18, Alice Wonder wrote:
> I apologize for continuing in the off-topic discussion.
> 
> On 08/28/2015 06:08 PM, Marc Chubbuck wrote:
>> AND With that all said, I am UNSUBSCRIBING FROM THIS LIST! I came to
>> this list hoping to LEARN and get HELP with CentOS, but instead, I am
>> getting plagued with this damn garbage. 30+ emails daily in the last
>> week or so is way too much. Maybe I can find more INTELLIGENT
>> conversation in the forums.
<<>>

actual, Marc, counting today, it is a total of 49 emails.

  the 25th = 02, 26th = 23, 27th = 22. 28th = 02

had you not posted, causing Alice to post to pacify you, it would have
been 47 and done with.


-- 
peace out.

If Bill Gates got a dime for every time Windows crashes...
 ...oh, wait. He does. THAT explains it!
-+-
in a world with out fences, who needs gates.

CentOS GNU/Linux 6.6

tc,hago.

g
.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] [off list] Re: please block user

[Alice Wonder]

I apologize for continuing in the off-topic discussion.

On 08/28/2015 06:08 PM, Marc Chubbuck wrote:

AND With that all said, I am UNSUBSCRIBING FROM THIS LIST! I came to
this list hoping to LEARN and get HELP with CentOS, but instead, I am
getting plagued with this damn garbage. 30+ emails daily in the last
week or so is way too much. Maybe I can find more INTELLIGENT
conversation in the forums.

On 8/27/2015 2:00 PM, Alice Wonder wrote:

*snip*

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] please block user

[Marc Chubbuck]

AND With that all said, I am UNSUBSCRIBING FROM THIS LIST! I came to 
this list hoping to LEARN and get HELP with CentOS, but instead, I am 
getting plagued with this damn garbage. 30+ emails daily in the last 
week or so is way too much. Maybe I can find more INTELLIGENT 
conversation in the forums.


On 8/27/2015 2:00 PM, Alice Wonder wrote:



On 08/27/2015 10:56 AM, g wrote:



On 08/27/15 12:12, Alice Wonder wrote:

On 08/27/2015 08:58 AM, g wrote:

On 08/27/15 09:31, m.r...@5-cent.us wrote:
<>


*sigh*
And they're probably sent by a script running on the PC of a fat,
47 yr old guy living in a basement and making money this way


.
i seriously doubt it.

several of the responses could not have been from a fat 47 yo guy.


Whoever he is, is using both valid SPF records and DKIM signatures,
they've figured out using those reduces spam score on some systems.


.
as i wrote;

several of the responses could not have been from a fat 47 yo guy.

the responses were too quick. no fat 47 yog could have enough photos
to respond to request that i made.


Okay, um, I have done some work related to that industry - never for a 
company that spams.


For about $10 you can buy photosets, usually of Eastern European 
models, with hundreds of photos in different settings.


So no, the photos are most certainly not an indication of who you were 
communicating with.


But enough off-topic. Those kind of e-mails should only be sent to 
people who specifically opt-in to receive them. That's the bottom line.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos




--
Marc Chubbuck Sr.
American Legion
Sr. Vice Commander
Gales Ferry - Ledyard Post 205
(860) 440-6420

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[Jonathan Billings]

On Aug 28, 2015, at 6:00 PM, Valeri Galtsev  wrote:
> The only way I've found in the past that is not total waste of
> my time is: block e-mail from the whole block of IPs of that provider.

Blocking all of digitalocean.com?

I guess that’s fine if you don’t mind having mostly false negatives.  You’d be 
better off teaching your antispam system to treat the netblock with more 
suspicion.  The spam I got had enough other rules that it was already in the 
“maybe spam” score, I bet if I created a spamassasin rule for it, it’d push it 
over the top.

--
Jonathan Billings 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[Valeri Galtsev]

On Fri, August 28, 2015 4:28 pm, John R Pierce wrote:
> On 8/28/2015 2:21 PM, Tim Dunphy wrote:
>> Here's the headers for one of the spam responses I got from the list:
>>
>> from:Tracyreply-to:tracy12...@safeloves.com
>> to:Tim Dunphy
>> date:Fri, Aug 28, 2015 at 2:19 PMsubject:Re: [CentOS] apache mysterious
>> 404
>> errormailed-by:safeloves.comsigned-by:safeloves.com:Important mainly
>> because it was sent directly to you.
>>
>> Please let me know if that's not what you're looking for!
>
> typically, you need the 'recieved from' headers so we can tell where it
> entered your mail system to block spammers.
>

Well, this is second discussion on this subject during last fortnight, and
I felt to stay away from it... But I just would add one thing. Blocking
originator of messages as John suggests, will work. The only thing about
it is: these are single IP domains, and one can easily keep registering
new ones, and this is all doable withing the frame digitalocean's (the IP
block owner) business model. Attempting to fight on per one case basis
with something that can be scripted on the bad guys' side I found counter
productive. The only way I've found in the past that is not total waste of
my time is: block e-mail from the whole block of IPs of that provider.

This can be done on the side of those being abused. Nothing as a mater of
fact can be done on the side of CentOS, and I really regret us wasting
Fabian's precious time on this. This is however really serious decision,
as you may block some of domains hosted at digitalocean your users may
need to communicate with. So, use your own judgement and caution. Grepping
your mail logs for long time back is advisable, but by no means can be
sufficient for sane decision. Contacting digitalocean with complaints,
hm..., though is right thing to do, but quite unlikely will lead to them
identifying the "person" and dealing with that person with whole
seriousness. IMHO, this last doesn't fit into their business model.

Just my $0.02

Valeri


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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[John R Pierce]

On 8/28/2015 2:21 PM, Tim Dunphy wrote:

Here's the headers for one of the spam responses I got from the list:

from:Tracyreply-to:tracy12...@safeloves.com
to:Tim Dunphy
date:Fri, Aug 28, 2015 at 2:19 PMsubject:Re: [CentOS] apache mysterious 404
errormailed-by:safeloves.comsigned-by:safeloves.com:Important mainly
because it was sent directly to you.

Please let me know if that's not what you're looking for!


typically, you need the 'recieved from' headers so we can tell where it 
entered your mail system to block spammers.




--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[Tim Dunphy]

Hey Fabian,

Here's the headers for one of the spam responses I got from the list:

from:Tracy reply-to:tracy12...@safeloves.com
to:Tim Dunphy 
date:Fri, Aug 28, 2015 at 2:19 PMsubject:Re: [CentOS] apache mysterious 404
errormailed-by:safeloves.comsigned-by:safeloves.com:Important mainly
because it was sent directly to you.

Please let me know if that's not what you're looking for!

Thanks,
Tim

On Fri, Aug 28, 2015 at 5:18 PM, Fabian Arrotin  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 28/08/15 22:24, John R Pierce wrote:
> > On 8/28/2015 1:21 PM, Robert Wolfe wrote:
> >> I've been getting that intermittently during the day today.
> >
> > I haven't seen any since I put the sending domain with a 'DISCARD'
> > in my /etc/mail/access database (using sendmail here)
> >
>
> Well, is there another domain involved now ? It seems the previous
> spammer (using multiple VMs on DigitalOcean network) had been blocked.
> As nothing is sent through the mailman/centos.org server, I can't even
> look at logs, but if you have useful informations (like some headers),
> feel free to forward those to me (and not on the list).
>
> Cheers,
>
> - --
> Fabian Arrotin
> The CentOS Project | http://www.centos.org
> gpg key: 56BEC54E | twitter: @arrfab
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iEYEARECAAYFAlXg0D4ACgkQnVkHo1a+xU5OnACggUMg3QikAFsgAAeHSGGGI5Q1
> 5MgAn2leYj3Wbflv1w8gHnNICEEOKOo3
> =rEWD
> -END PGP SIGNATURE-
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[Fabian Arrotin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/08/15 22:24, John R Pierce wrote:
> On 8/28/2015 1:21 PM, Robert Wolfe wrote:
>> I've been getting that intermittently during the day today.
> 
> I haven't seen any since I put the sending domain with a 'DISCARD'
> in my /etc/mail/access database (using sendmail here)
> 

Well, is there another domain involved now ? It seems the previous
spammer (using multiple VMs on DigitalOcean network) had been blocked.
As nothing is sent through the mailman/centos.org server, I can't even
look at logs, but if you have useful informations (like some headers),
feel free to forward those to me (and not on the list).

Cheers,

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlXg0D4ACgkQnVkHo1a+xU5OnACggUMg3QikAFsgAAeHSGGGI5Q1
5MgAn2leYj3Wbflv1w8gHnNICEEOKOo3
=rEWD
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[m . roth]

Tim Dunphy wrote:
> Hey guys,
>
>  I just noticed this recently in my latest posts to the list. But I've
> noticed that every time I mail the list for some advice, I get hit with
> spam from a camgirl site like every other message. Kinda funny actually.
> But also annoying!! Anyone else experience this?
>
> Maybe this is something the admins/moderators can take care of!
>
I would guess that someone, or a bot, joined the list for the sole purpose
of harvesting email addresses, and I can't see how the admins can possibly
block that.

And, btw, this is where I mostly post using this email address, and no,
I'm not sending spam to France, or southeast Asia, or (as in, they put
my email as their Reply-To:).

mark "ah, for the old days of fair use"

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[John R Pierce]

On 8/28/2015 1:21 PM, Robert Wolfe wrote:

I've been getting that intermittently during the day today.


I haven't seen any since I put the sending domain with a 'DISCARD' in my 
/etc/mail/access database (using sendmail here)


--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] camgirl spam on the list

[Robert Wolfe]

I've been getting that intermittently during the day today.

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Tim Dunphy
Sent: Friday, August 28, 2015 2:53 PM
To: CentOS mailing list 
Subject: [CentOS] camgirl spam on the list

Hey guys,

 I just noticed this recently in my latest posts to the list. But I've noticed 
that every time I mail the list for some advice, I get hit with spam from a 
camgirl site like every other message. Kinda funny actually.
But also annoying!! Anyone else experience this?

Maybe this is something the admins/moderators can take care of!

Thanks,
Tim

--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] GNU bc base conversion

[Warren Young]

On Aug 28, 2015, at 9:50 AM, Gordon Messmer  wrote:
> 
> On 08/28/2015 07:15 AM, Mike - st257 wrote:
>> Thoughts as to why my BC functions aren't properly converting between bases?
>> 
>> Decimal to binary or hex works fine, but not binary or hex to decimal and
>> so forth.
> 
> I'm not an expert in bc, so I might be wrong, but it looks like setting the 
> ibase inside a function is simply too late.  ibase affects how bc interprets 
> input.

Yes, and it’s a serious design mistake in bc, IMHO.  No other programmable 
system I’ve ever used changes how numbers in program text are interpreted based 
on prior commands to the system.

I wrote a long answer explaining this on the Unix & Linux Stack Exchange here:

  http://unix.stackexchange.com/a/199620
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Tim Dunphy]

Guys,

We actually found the problem. The problem was actually in a javascript
file. It was referring to it's parent directory as mycompanyStore. So once
I noticed that, I went into that directory and created a symlink.

ln -s . mycompanyStore from within that directory. That let the java script
know that the directory it was in was actually the one that it wanted.
Before that was done Apache was looking for the image files in
/var/www/mycompanyStore/mycompanyStore/images/foo.img

Once I put that symlink in place, that actually corrected the problem. So I
told the developer what I'd done and she fixed the JS to end up with the
same effect. So now the problem is fixed!

Anyway, I really do appreciate the support you guys are always ready with
on the list!!

Thanks,
Tim

On Fri, Aug 28, 2015 at 1:06 PM, Tony Mountifield 
wrote:

> In article <0f55e883640c125375c75...@ritz.innovate.net>,
> Richard  wrote:
> >
> > Also need to see the error_log entries from the back-end httpd
> > server that's serving from the documentroot. The proxy server's logs
> > (whether it should be there or not) only show the proxy issues, not
> > the issues that are causing the 404s, so aren't really relevant to
> > the 404 issue. The back-end server's logs will indicate why the file
> > can't be found, or generally at least pretty good hints.
>
> The first question is: are there even a separate back-end and front-end,
> or is it just a single server that is misconfigured and is trying to do
> proxy operations when it shouldn't? It sounds to me like the latter.
>
> Cheers
> Tony
> --
> Tony Mountifield
> Work: t...@softins.co.uk - http://www.softins.co.uk
> Play: t...@mountifield.org - http://tony.mountifield.org
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] camgirl spam on the list

[Tim Dunphy]

Hey guys,

 I just noticed this recently in my latest posts to the list. But I've
noticed that every time I mail the list for some advice, I get hit with
spam from a camgirl site like every other message. Kinda funny actually.
But also annoying!! Anyone else experience this?

Maybe this is something the admins/moderators can take care of!

Thanks,
Tim

-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Tony Mountifield]

In article <0f55e883640c125375c75...@ritz.innovate.net>,
Richard  wrote:
> 
> Also need to see the error_log entries from the back-end httpd
> server that's serving from the documentroot. The proxy server's logs
> (whether it should be there or not) only show the proxy issues, not
> the issues that are causing the 404s, so aren't really relevant to
> the 404 issue. The back-end server's logs will indicate why the file
> can't be found, or generally at least pretty good hints.

The first question is: are there even a separate back-end and front-end,
or is it just a single server that is misconfigured and is trying to do
proxy operations when it shouldn't? It sounds to me like the latter.

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Richard]

> Date: Friday, August 28, 2015 16:47:43 +
> From: Tony Mountifield 
>
> In article
>  m>, Tim Dunphy  wrote:
>> Hey guys,
>> 
>>  Sorry for the failed attempts at obscuring the company I work
>>  for. My boss wouldn't take too kindly to it if I revealed that
>> information on a mailing list. :)
> 
> It's easily deducible from the IP addresses anyway...
> 
>> So anyway, I realized that capitalization might be the problem.
>> So I renamed the directory to match what was in the URL. That
>> didn't solve the problem.
>> 
>> However I noticed this message turning up in the logs:
>> 
>> [Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid
>> 139661984888576] [client 173.213.212.234:14579] AH01144: No
>> protocol handler was valid for the URL
>> /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you are using a
>> DSO version of mod_proxy, make sure the proxy submodules are
>> included in the configuration using LoadModule., referer:
>> http://stage.theshopatmycompanystudios.com/
>> 
>> [...etc...]
>> 
>> So taking the advice of that eror I tried enabling all the proxy
>> modules in the apache config:
>> 
>> 
>> LoadModule proxy_module modules/mod_proxy.so
>> 
>> LoadModule proxy_connect_module modules/mod_proxy_connect.so
>> 
>> LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
>> 
>> LoadModule proxy_http_module modules/mod_proxy_http.so
>> 
>> LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
>> 
>> 
>> But those files are still 404ing. Not sure where to take it from
>> here. I'd appreciate any help you can give!
> 
> Well if it's a single web server that you want to serve its own
> files, it shouldn't be doing any proxy operations anyway. So
> rather than enabling proxy modules, it would be better to
> understand why it is trying to do a proxy operation.
> 
> It's hard to help further without seeing your http config files in
> /etc/http/conf and /etc/http/conf.d. To save space, you can filter
> out all comments and blank lines like this:
> 
># grep '^ *[^# ]' /etc/httpd/conf/httpd.conf
># /etc/httpd/conf.d/*.conf >/tmp/http-config.txt
> 
> That will output all lines that start with zero or more spaces
> followed by at least one character that is not a space or a hash.
> It will also precede each line with the name of the file it is in.
> 
> You can then edit /tmp/http-config.txt with some global replaces
> if you want to obscure the domain name and document root names,
> and post the result.
> 
> Cheers
> Tony

Also need to see the error_log entries from the back-end httpd
server that's serving from the documentroot. The proxy server's logs
(whether it should be there or not) only show the proxy issues, not
the issues that are causing the 404s, so aren't really relevant to
the 404 issue. The back-end server's logs will indicate why the file
can't be found, or generally at least pretty good hints.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Tony Mountifield]

In article ,
Tim Dunphy  wrote:
> Hey guys,
> 
>  Sorry for the failed attempts at obscuring the company I work for. My boss
> wouldn't take too kindly to it if I revealed that information on a mailing
> list. :)

It's easily deducible from the IP addresses anyway...

> So anyway, I realized that capitalization might be the problem. So I
> renamed the directory to match what was in the URL. That didn't solve the
> problem.
> 
> However I noticed this message turning up in the logs:
> 
> [Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid
> 139661984888576] [client 173.213.212.234:14579] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
> 
> [...etc...]
> 
> So taking the advice of that eror I tried enabling all the proxy modules in
> the apache config:
> 
> 
> LoadModule proxy_module modules/mod_proxy.so
> 
> LoadModule proxy_connect_module modules/mod_proxy_connect.so
> 
> LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
> 
> LoadModule proxy_http_module modules/mod_proxy_http.so
> 
> LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
> 
> 
> But those files are still 404ing. Not sure where to take it from here. I'd
> appreciate any help you can give!

Well if it's a single web server that you want to serve its own files, it
shouldn't be doing any proxy operations anyway. So rather than enabling
proxy modules, it would be better to understand why it is trying to do a
proxy operation.

It's hard to help further without seeing your http config files in
/etc/http/conf and /etc/http/conf.d. To save space, you can filter out all
comments and blank lines like this:

# grep '^ *[^# ]' /etc/httpd/conf/httpd.conf /etc/httpd/conf.d/*.conf 
>/tmp/http-config.txt

That will output all lines that start with zero or more spaces followed by
at least one character that is not a space or a hash. It will also precede
each line with the name of the file it is in.

You can then edit /tmp/http-config.txt with some global replaces if you
want to obscure the domain name and document root names, and post the
result.

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [OT] GNU bc base conversion

[Gordon Messmer]

On 08/28/2015 07:15 AM, Mike - st257 wrote:

Thoughts as to why my BC functions aren't properly converting between bases?

Decimal to binary or hex works fine, but not binary or hex to decimal and
so forth.


I'm not an expert in bc, so I might be wrong, but it looks like setting 
the ibase inside a function is simply too late.  ibase affects how bc 
interprets input.  So "echo "bin_to_dec(1001)" | bc" is going to 
interpret the value of 1001 while reading it from input, not after 
passing it to a function where ibase is reset.


Supporting that theory:
$ bc
...
define bin_to_dec(b) { obase=10; ibase=2; return b; }
bin_to_dec(1001)
1001

Decimal to binary and hex work correctly because decimal input is the 
default.  Since ibase is already 10, those values are interpreted the 
way you want, but not because you're setting ibase in your function.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Robert Wolfe]

Where are the rest of the site's documents store?  In /var/www/html?


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Tim Dunphy
Sent: Friday, August 28, 2015 10:20 AM
To: CentOS mailing list 
Subject: Re: [CentOS] apache mysterious 404 error

Hi Robert,

It's this:

drwxr-xr-x. 2 daemon daemon 4096 Aug 27 12:34 /var/www/mycompanyStore/images


Thanks,

Tim

On Fri, Aug 28, 2015 at 11:17 AM, Robert Wolfe 
wrote:

> What is the absolute path on the server that /mycompanyStore/images/ 
> is store in?
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On 
> Behalf Of Tim Dunphy
> Sent: Friday, August 28, 2015 10:12 AM
> To: CentOS mailing list 
> Subject: Re: [CentOS] apache mysterious 404 error
>
> Hey guys,
>
>  Sorry for the failed attempts at obscuring the company I work for. My 
> boss wouldn't take too kindly to it if I revealed that information on 
> a mailing list. :)
>
> So anyway, I realized that capitalization might be the problem. So I 
> renamed the directory to match what was in the URL. That didn't solve 
> the problem.
>
> However I noticed this message turning up in the logs:
>
> [Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid 
> 139661984888576] [client 173.213.212.234:14579] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:30.057216 2015] [proxy:warn] [pid 23780:tid 
> 139661995378432] [client 173.213.212.234:14577] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377172 2015] [proxy:warn] [pid 23890:tid 
> 139661827540736] [client 173.213.212.234:2425] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/altImg.png. If 
> you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377269 2015] [proxy:warn] [pid 23889:tid 
> 139661942929152] [client 173.213.212.234:2426] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377384 2015] [proxy:warn] [pid 23889:tid 
> 139661953419008] [client 173.213.212.234:2427] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.382079 2015] [proxy:warn] [pid 23891:tid 
> 139662047827712] [client 173.213.212.234:2430] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.750944 2015] [proxy:warn] [pid 23977:tid 
> 139661911459584] [client 173.213.212.234:6011] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/altImg.png. If 
> you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.751086 2015] [proxy:warn] [pid 23978:tid 
> 139662016358144] [client 173.213.212.234:6013] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.755018 2015] [proxy:warn] [pid 23977:tid 
> 139661890479872] [client 173.213.212.234:6012] AH01144: No protocol 
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy 
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.755120 2015] [proxy:warn] [pid 23978:tid 
> 139662005868288] [client 173.213.212.234:6014] AH01144: No protocol 
> handler was valid f

Re: [CentOS] apache mysterious 404 error

[Tim Dunphy]

Hi Robert,

It's this:

drwxr-xr-x. 2 daemon daemon 4096 Aug 27 12:34 /var/www/mycompanyStore/images


Thanks,

Tim

On Fri, Aug 28, 2015 at 11:17 AM, Robert Wolfe 
wrote:

> What is the absolute path on the server that /mycompanyStore/images/ is
> store in?
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Tim Dunphy
> Sent: Friday, August 28, 2015 10:12 AM
> To: CentOS mailing list 
> Subject: Re: [CentOS] apache mysterious 404 error
>
> Hey guys,
>
>  Sorry for the failed attempts at obscuring the company I work for. My
> boss wouldn't take too kindly to it if I revealed that information on a
> mailing list. :)
>
> So anyway, I realized that capitalization might be the problem. So I
> renamed the directory to match what was in the URL. That didn't solve the
> problem.
>
> However I noticed this message turning up in the logs:
>
> [Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid
> 139661984888576] [client 173.213.212.234:14579] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:30.057216 2015] [proxy:warn] [pid 23780:tid
> 139661995378432] [client 173.213.212.234:14577] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy
> submodules are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377172 2015] [proxy:warn] [pid 23890:tid
> 139661827540736] [client 173.213.212.234:2425] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/altImg.png. If you are
> using a DSO version of mod_proxy, make sure the proxy submodules are
> included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377269 2015] [proxy:warn] [pid 23889:tid
> 139661942929152] [client 173.213.212.234:2426] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.377384 2015] [proxy:warn] [pid 23889:tid
> 139661953419008] [client 173.213.212.234:2427] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:27:43.382079 2015] [proxy:warn] [pid 23891:tid
> 139662047827712] [client 173.213.212.234:2430] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.750944 2015] [proxy:warn] [pid 23977:tid
> 139661911459584] [client 173.213.212.234:6011] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/altImg.png. If you are
> using a DSO version of mod_proxy, make sure the proxy submodules are
> included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.751086 2015] [proxy:warn] [pid 23978:tid
> 139662016358144] [client 173.213.212.234:6013] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.755018 2015] [proxy:warn] [pid 23977:tid
> 139661890479872] [client 173.213.212.234:6012] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
> [Fri Aug 28 01:28:01.755120 2015] [proxy:warn] [pid 23978:tid
> 139662005868288] [client 173.213.212.234:6014] AH01144: No protocol
> handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
> If you are using a DSO version of mod_proxy, make sure the proxy submodules
> are included in the configuration using LoadModule., referer:
> http://stage.theshopatmycompanystudios.com/
>
>
> So taking the advice of that eror I tried enabling all the proxy modules
> in the apache con

Re: [CentOS] apache mysterious 404 error

[Robert Wolfe]

What is the absolute path on the server that /mycompanyStore/images/ is store 
in?

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Tim Dunphy
Sent: Friday, August 28, 2015 10:12 AM
To: CentOS mailing list 
Subject: Re: [CentOS] apache mysterious 404 error

Hey guys,

 Sorry for the failed attempts at obscuring the company I work for. My boss 
wouldn't take too kindly to it if I revealed that information on a mailing 
list. :)

So anyway, I realized that capitalization might be the problem. So I renamed 
the directory to match what was in the URL. That didn't solve the problem.

However I noticed this message turning up in the logs:

[Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid 139661984888576] 
[client 173.213.212.234:14579] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules are 
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:30.057216 2015] [proxy:warn] [pid 23780:tid 139661995378432] 
[client 173.213.212.234:14577] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules are 
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377172 2015] [proxy:warn] [pid 23890:tid 139661827540736] 
[client 173.213.212.234:2425] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/altImg.png. If you are using a DSO version of 
mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377269 2015] [proxy:warn] [pid 23889:tid 139661942929152] 
[client 173.213.212.234:2426] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you are using a DSO 
version of mod_proxy, make sure the proxy submodules are included in the 
configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377384 2015] [proxy:warn] [pid 23889:tid 139661953419008] 
[client 173.213.212.234:2427] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you are using a DSO version 
of mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.382079 2015] [proxy:warn] [pid 23891:tid 139662047827712] 
[client 173.213.212.234:2430] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you are using a DSO version 
of mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.750944 2015] [proxy:warn] [pid 23977:tid 139661911459584] 
[client 173.213.212.234:6011] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/altImg.png. If you are using a DSO version of 
mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.751086 2015] [proxy:warn] [pid 23978:tid 139662016358144] 
[client 173.213.212.234:6013] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you are using a DSO 
version of mod_proxy, make sure the proxy submodules are included in the 
configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755018 2015] [proxy:warn] [pid 23977:tid 139661890479872] 
[client 173.213.212.234:6012] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you are using a DSO version 
of mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755120 2015] [proxy:warn] [pid 23978:tid 139662005868288] 
[client 173.213.212.234:6014] AH01144: No protocol handler was valid for the 
URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you are using a DSO version 
of mod_proxy, make sure the proxy submodules are included in the configuration 
using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/


So taking the advice of that eror I tried enabling all the proxy modules in the 
apache config:


LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_connect_module modules/mod_proxy_connect.so

LoadModule proxy_ftp_module modules/mod_proxy_ftp.so

LoadModule proxy_http_module modules/mod_proxy_http.so

LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so


But those files are 

Re: [CentOS] apache mysterious 404 error

[Tim Dunphy]

Hey guys,

 Sorry for the failed attempts at obscuring the company I work for. My boss
wouldn't take too kindly to it if I revealed that information on a mailing
list. :)

So anyway, I realized that capitalization might be the problem. So I
renamed the directory to match what was in the URL. That didn't solve the
problem.

However I noticed this message turning up in the logs:

[Fri Aug 28 01:27:30.057020 2015] [proxy:warn] [pid 23782:tid
139661984888576] [client 173.213.212.234:14579] AH01144: No protocol
handler was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules
are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:30.057216 2015] [proxy:warn] [pid 23780:tid
139661995378432] [client 173.213.212.234:14577] AH01144: No protocol
handler was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg.
If you are using a DSO version of mod_proxy, make sure the proxy submodules
are included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377172 2015] [proxy:warn] [pid 23890:tid
139661827540736] [client 173.213.212.234:2425] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/altImg.png. If you are using a
DSO version of mod_proxy, make sure the proxy submodules are included in
the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377269 2015] [proxy:warn] [pid 23889:tid
139661942929152] [client 173.213.212.234:2426] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.377384 2015] [proxy:warn] [pid 23889:tid
139661953419008] [client 173.213.212.234:2427] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:27:43.382079 2015] [proxy:warn] [pid 23891:tid
139662047827712] [client 173.213.212.234:2430] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.750944 2015] [proxy:warn] [pid 23977:tid
139661911459584] [client 173.213.212.234:6011] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/altImg.png. If you are using a
DSO version of mod_proxy, make sure the proxy submodules are included in
the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.751086 2015] [proxy:warn] [pid 23978:tid
139662016358144] [client 173.213.212.234:6013] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_485x1215_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755018 2015] [proxy:warn] [pid 23977:tid
139661890479872] [client 173.213.212.234:6012] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_792x413_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/

[Fri Aug 28 01:28:01.755120 2015] [proxy:warn] [pid 23978:tid
139662005868288] [client 173.213.212.234:6014] AH01144: No protocol handler
was valid for the URL /mycompanyStore/images/Jimmy_792x802_R2.jpg. If you
are using a DSO version of mod_proxy, make sure the proxy submodules are
included in the configuration using LoadModule., referer:
http://stage.theshopatmycompanystudios.com/


So taking the advice of that eror I tried enabling all the proxy modules in
the apache config:


LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_connect_module modules/mod_proxy_connect.so

LoadModule proxy_ftp_module modules/mod_proxy_ftp.so

LoadModule proxy_http_module modules/mod_proxy_http.so

LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so


But those files are still 404ing. Not sure where to take it from here. I'd
appreciate any help you can give!


Thanks

On Fri, Aug 28, 2015 at 10:00 AM, Robert Wolfe 
wrote:

> Check the links again.  Remove the * from images*/ and you should be all
> set.
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Tim Dunp

[CentOS] [OT] GNU bc base conversion

[Mike - st257]

Hello CentOS List Members,

Thoughts as to why my BC functions aren't properly converting between bases?

Decimal to binary or hex works fine, but not binary or hex to decimal and
so forth.
No doubt the syntax is in some way wrong, but when I test from the CLI and
the right values are returned, I have to wonder.

Other than a few other define statements, the only other option I have set
is scale=5 in my bcrc.

In reference to the order of (o|i)base parameters, I have specified obase
before ibase [0].
[0] http://docstore.mik.ua/orelly/unix/upt/ch49_03.htm

See below for my examples.
Thanks!



]$ echo "bin_to_dec(1001)" | bc
1001
# should be decimal 9

]$ echo "obase=10; ibase=2; 1001" | bc
9

]$ grep bin_to_dec ~/.bcrc
define bin_to_dec(b) { obase=10; ibase=2; return b; }



]$ echo "hex_to_dec(AB)" | bc
99
# should be decimal 171

]$ echo "obase=10; ibase=16; AB" | bc
171
]$ echo "obase=A; ibase=16; AB" | bc
171

]$ grep hex_to_dec ~/.bcrc
define hex_to_dec(h) { obase=A; ibase=16; return h; }

-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apache mysterious 404 error

[Robert Wolfe]

Check the links again.  Remove the * from images*/ and you should be all set.

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Tim Dunphy
Sent: Thursday, August 27, 2015 5:18 PM
To: CentOS mailing list 
Subject: [CentOS] apache mysterious 404 error

Hey guys,

 Just have a question about apache. Hoping to get an opinion on this.

 I've just setup a site under apache 2.4.

 And made sure that the document root setup in the vhost for the site I'm 
serving has permissions for the apache user. Yet some of the files are throwing 
a 404 error in a browser even tho they are clearly present and accounted for on 
the file system.

For example, I'm getting this error:

(index):1 GET 
http://stage.theshopatmycomany.com/mycomanyStore/images*/altImg.png
404 (*Not Found)

(index):1 GET 
http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_485x1215_R2.jpg
404* (Not Found)

(index):1 GET 
http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x802_R2.jpg
404* (Not Found)

(index):1 GET 
http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x413_R2.jpg
404* (Not Found)
And yet as I mentioned all those files are definitely there on the file
system:

[root@aozwsls00019la apache2]# ls -l
/var/www/mycomanystore/images/altImg.png
/var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
/var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
/var/www/mycomanystore/images/Jimmy_792x413_R2.jpg

-rw-r--r--. 1 daemon daemon128 Aug 27 12:22
/var/www/mycomanystore/images/altImg.png

-rw-r--r--. 1 daemon daemon 260983 Jul 16 14:03 
/var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg

-rw-r--r--. 1 daemon daemon 126628 Jul 16 14:00 
/var/www/mycomanystore/images/Jimmy_792x413_R2.jpg

-rw-r--r--. 1 daemon daemon 222568 Jul 16 13:56 
/var/www/mycomanystore/images/Jimmy_792x802_R2.jpg

And all those files have the correct ownership for apache:

[root@aozwsls00019la apache2]# egrep -i "user|group" conf/httpd.conf | egrep -i 
-v -e '#' -e log -e module

User daemon

Group daemon

All the files are owned by daemon:daemon!! So why on earth are these files 
giving a 404?

This is my virtual host for the site:




ServerAdmin timothy.dun...@mycomany.com

DocumentRoot /var/www/mycomanystore

ServerName stage.theshopatmycomanystudios.com

ServerAlias 173.213.219.48

ErrorLog logs/store_error_log

LogFormat "%h %l %u %t \"%r\" %>s %b" common

CustomLog logs/store_access_log common



  DirectoryIndex index.html

  AddHandler cgi-script .cgi

  Options -Indexes +FollowSymLinks +ExecCGI +Includes

  AllowOverride All

  Require all granted



ExpiresActive On

ExpiresDefault "access plus 30 minute"

RewriteEngine On

RewriteCond %{REQUEST_METHOD} ^TRACE

RewriteRule .* - [F]



Thanks

Tim


--
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Cisco UCS HBA Firmware - 1.6.0.12(b)

[Jonathan Billings]

On Fri, Aug 28, 2015 at 09:32:10AM +0530, Saravanan Arumugam wrote:
> Any idea when Cisco UCS Firmware Package will be included in centos
> Patching ? 
> 
> I had planned for Ontab storage upgarde, hence needed this level
> firmware version on CentOS 
> 
> Any help and leads will help me to plan the upgrade.

What's the package name?  Is it included in RHEL, or is it a package
in the CentOS Extras repo?

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] regenerating /var/lib/logrotate.status

[Robert Moskowitz]

I had a system date problem when logrotate ran for the first time such 
that /var/lib/logrotate.status has:


logrotate state -- version 2
"/var/log/yum.log" 1970-1-1-0:0:0
"/var/log/wtmp" 1970-1-1-0:0:0
"/var/log/chrony/*.log" 1970-1-1-0:0:0
"/var/log/spooler" 1970-1-1-0:0:0
"/var/log/btmp" 1970-1-1-0:0:0
"/var/log/maillog" 1970-1-1-0:0:0
"/var/log/wpa_supplicant.log" 1970-1-1-0:0:0
"/var/log/secure" 1970-1-1-0:0:0
"/var/log/ppp/connect-errors" 1970-1-1-0:0:0
"/var/log/messages" 1970-1-1-0:0:0
"/var/log/cron" 1970-1-1-0:0:0

MOST of these files now have good dates (btmp still old date).

I assume I can use:  'touch file' to make the date current (as in the 
case of /var/log/btmp).


But how do I regenerate this file so that logrotate will run?

thanks


How can I regen
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 126, Issue 12

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2015:1682 Important CentOS 7 thunderbird Security Update
  (Johnny Hughes)
   2. CESA-2015:1682 Important CentOS 6 thunderbird Security Update
  (Johnny Hughes)
   3. CESA-2015:1682 Important CentOS 5 thunderbird Security Update
  (Johnny Hughes)
   4. CEBA-2015:1690 CentOS 7 kross-interpretersFASTTRACK BugFix
  Update (Johnny Hughes)
   5. CESA-2015:1693 Critical CentOS 7 firefox Security Update
  (Johnny Hughes)
   6. CESA-2015:1693 Critical CentOS 6 firefox Security Update
  (Johnny Hughes)
   7. CESA-2015:1693 Critical CentOS 5 firefox Security Update
  (Johnny Hughes)
   8. Infra : TLS redirection for lists.centos.org (Fabian Arrotin)


--

Message: 1
Date: Tue, 25 Aug 2015 22:25:27 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2015:1682 Important CentOS 7
thunderbird Security Update
Message-ID: <20150825222527.ga52...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2015:1682 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1682.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
492a01e64a18f0d1800361dfd73d9678a07ce1c1eb75908e1c2c6a77dec9bfd8  
thunderbird-38.2.0-1.el7.centos.x86_64.rpm

Source:
2a4b617361ac4ba011498b67672a799e315d1db60db9804a63af67efbe454380  
thunderbird-38.2.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Tue, 25 Aug 2015 22:30:07 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2015:1682 Important CentOS 6
thunderbird Security Update
Message-ID: <20150825223007.ga52...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2015:1682 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1682.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
212a3fb8ffd55e5b884a0d3d4a93b9fa329e42ec0d3da2697cd07f4164cab75d  
thunderbird-38.2.0-4.el6.centos.i686.rpm

x86_64:
2f599516b2700248194b1b0349de15698e6d5834417c78e4d9de1541033bca97  
thunderbird-38.2.0-4.el6.centos.x86_64.rpm

Source:
02c890e4584b486f07a69663e905d4658aa623f1bd38f8ff107707324a06962f  
thunderbird-38.2.0-4.el6.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 3
Date: Tue, 25 Aug 2015 23:21:00 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2015:1682 Important CentOS 5
thunderbird Security Update
Message-ID: <20150825232059.ga11...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2015:1682 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1682.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
4a3c17746a0f6eb4538da53dedb6ce365d7e26b3922ca2764ad95cb6552985be  
thunderbird-38.2.0-4.el5.centos.i386.rpm

x86_64:
085dda14f0c68b842c7b691e9ae8797cab53e0d4b9f21d6b739b023f53181e2d  
thunderbird-38.2.0-4.el5.centos.x86_64.rpm

Source:
caa0713b07db9133ad60279eebf11190f87a1113c9142276756f8cbbe8e1cd50  
thunderbird-38.2.0-4.el5.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 4
Date: Thu, 27 Aug 2015 20:20:35 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2015:1690 CentOS 7 kross-interpreters
FASTTRACK BugFix Update
Message-ID: <20150827202035.ga37...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2015:1690 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-1690.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
bff85d28d1892ca118dbd646a6f8c8b6e5bf954c282f8bcd424ce55c33cad0bd  
kross-interpreters-4.10.5-8.el7.x86_64.rpm
0dccd9630de7c99e87a7ed2b8e1a8bccfe2c

Re: [CentOS] apache mysterious 404 error

[Tony Mountifield]

Hi Tim,

It really helps both the web server and us if you are consistent with both
spelling and capitalisation. I don't know whether you retyped stuff into
your posting or copied and pasted it, but if you look below you will see
at least these variations:

/mycopmanyStore/
/mycompanystore/
/mycpmpanystore/
/mycompanyStore/

And your original posting showed the path as containing /mycomanystore/ 
(without p)

Always copy-and-paste if possible, rather than inaccurately re-typing, so
we are not trying to help you with the wrong problem!

In addition, if you are indeed using symlinks to point at the real directories
or files, you need to make sure that Options FollowSymLinks is enabled in your
httpd configuration file.

Cheers
Tony

In article ,
Tim Dunphy  wrote:
> Hey Rodrigo,
> 
> Thanks for your reply.
> 
> Well those errors are pulled from the Chrome developer tools.
> 
>  I notice if I do a GET on that file using both all lower case as well as
> the upper case that's in the URL I get the same result:
> 
> [root@aozwsls00019la apache2]# GET
> http://stage.theshopatmycompanystudios.com/mycopmanyStore/images/altImg.png
> 
> 
> 404 Not Found
> 
> Not Found
> The requested URL /mycompanyStore/images/altImg.png was not found on
> this server.
> 
> 
> [root@aozwsls00019la apache2]# GET
> http://stage.theshopatmycompanystudios.com/mycompanystore/images/altImg.png
> 
> 
> 404 Not Found
> 
> Not Found
> The requested URL /mycpmpanystore/images/altImg.png was not found on
> this server.
> 
> 
> This is how that file looks on the command line. I made a symlink to
> account for the change in case, because I realize that's relevant:
> 
> -rw-r--r--. 1 daemon daemon 128 Aug 27 12:22
> /var/www/nbcstore/images/altImg.png
> 
> -rw-r--r--. 1 daemon daemon 128 Aug 27 12:22
> /var/www/mycompanyStore/images/altImg.png
> 
> Still not sure why I'm not able to do a GET on that and those other files.
> Appreciate your input tho! And any other advice is certainly welcome!
> 
> Tim
> 
> On Thu, Aug 27, 2015 at 7:42 PM, Rodrigo Maia  wrote:
> 
> > Hi apache on GNU/Linux  is case-sensitive samples:
> >
> >
> > /var/www/mycomanystore/images/altImg.png
> > /var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
> > /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
> > /var/www/mycomanystore/images/Jimmy_792x413_R2.jpg
> >
> > on  browser :
> >
> >
> > (index):1 GET
> > http://stage.theshopatmycomany.com/mycomanyStore/images*/altImg.png
> >
> > try :
> >
> >
> > (index):1 GET
> > http://stage.theshopatmycomany.com/mycomanystore/images/altImg.png
> > 
> >
> >
> >
> > 2015-08-27 19:18 GMT-03:00 Tim Dunphy :
> >
> > > Hey guys,
> > >
> > >  Just have a question about apache. Hoping to get an opinion on this.
> > >
> > >  I've just setup a site under apache 2.4.
> > >
> > >  And made sure that the document root setup in the vhost for the site I'm
> > > serving has permissions for the apache user. Yet some of the files are
> > > throwing a 404 error in a browser even tho they are clearly present and
> > > accounted for on the file system.
> > >
> > > For example, I'm getting this error:
> > >
> > > (index):1 GET
> > > http://stage.theshopatmycomany.com/mycomanyStore/images*/altImg.png
> > > 404 (*Not Found)
> > >
> > > (index):1 GET
> > >
> > http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_485x1215_R2.jpg
> > > 404* (Not Found)
> > >
> > > (index):1 GET
> > >
> > http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x802_R2.jpg
> > > 404* (Not Found)
> > >
> > > (index):1 GET
> > >
> > http://stage.theshopatmycomany.com/mycomanyStore/images*/Jimmy_792x413_R2.jpg
> > > 404* (Not Found)
> > > And yet as I mentioned all those files are definitely there on the file
> > > system:
> > >
> > > [root@aozwsls00019la apache2]# ls -l
> > > /var/www/mycomanystore/images/altImg.png
> > > /var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
> > > /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
> > > /var/www/mycomanystore/images/Jimmy_792x413_R2.jpg
> > >
> > > -rw-r--r--. 1 daemon daemon128 Aug 27 12:22
> > > /var/www/mycomanystore/images/altImg.png
> > >
> > > -rw-r--r--. 1 daemon daemon 260983 Jul 16 14:03
> > > /var/www/mycomanystore/images/Jimmy_485x1215_R2.jpg
> > >
> > > -rw-r--r--. 1 daemon daemon 126628 Jul 16 14:00
> > > /var/www/mycomanystore/images/Jimmy_792x413_R2.jpg
> > >
> > > -rw-r--r--. 1 daemon daemon 222568 Jul 16 13:56
> > > /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
> > >
> > > And all those files have the correct ownership for apache:
> > >
> > > [root@aozwsls00019la apache2]# egrep -i "user|group" conf/httpd.conf |
> > > egrep -i -v -e '#' -e log -e module
> > >
> > > User daemon
> > >
> > > Group daemon
> > >
> > > All the files are owned by daemon:daemon!! So why on earth are these
> > files
> > > giving a 404?
> > >
> > > This is my virtual host for the site:
> > >
> > >
> > > 
> > >
> > > ServerAdmin timothy.dun...@m

Re: [CentOS] apache mysterious 404 error

[Richard]

 Original Message 
> Date: Friday, August 28, 2015 07:40:43 +0200
> From: Luigi Rosa 
>
> Tim Dunphy wrote on 28/08/2015 00:18:
> 
>>   And made sure that the document root setup in the vhost for the
>>   site I'm serving has permissions for the apache user. Yet some
>> of the files are throwing a 404 error in a browser even tho they
>> are clearly present and accounted for on the file system.
> 
> Put
> 
> CheckSpelling on
> CheckCaseOnly on
> 
> in vhost or Apache configuration
> 
> You have to enable mod_speling in
> /etc/httpd/conf.modules.d/00-base.conf

Please show relevant httpd error_log entries. What is displayed to
the client is never as useful as the real thing.

Separately, your documentroot directory and file ownerships are a
security risk:

   > -rw-r--r--. 1 daemon daemon 222568 Jul 16 13:56
  /var/www/mycomanystore/images/Jimmy_792x802_R2.jpg
 
   > And all those files have the correct ownership for apache:
 
   > [root@aozwsls00019la apache2]# egrep -i "user|group" 
   conf/httpd.conf 

   > User daemon
   > Group daemon

Directories and files under the documentroot need to be accessible
to the httpd process, but should never be owned or writable by it. 

If they are owned/writable by the httpd process and someone breaks
through (either a bug in httpd (apache) or more likely code/scripts
you are running) then the attacker can do as they wish with the
documentroot contents - including (but not limited to) defacing your
site. 

Also, "daemon" is an odd user to be running your httpd as. The
default is generally "apache". On my centos-5 and -6 servers (what
centos release are you running here?) "daemon" is a member of the
group "bin", which escalates potential security issues.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] centos 6 - changing resolv.conf by hand gets overwritten by rebooting

[Nicolas Thierry-Mieg]

On 08/27/2015 09:36 PM, George wrote:

given machine with C6 x86_64 (seen on C 6.6 but also before and probably
still present on C6.7) only 1 interface, there is dhcp on this network
(for kickstarting) but the machines have static ip's, and NO
networkmanager installed

contents of resolv.conf
search some.domain.here
nameserver x.x.x.x #dns1
nameserver y.y.y.y #dns2

change resolv.conf to:
search some.newdomain.here
nameserver z.z.z.z #dns3
nameserver a.a.a.a #dns4

reboot machine and the contents of resolv.conf is again:
search some.domain.here
nameserver x.x.x.x #dns1
nameserver y.y.y.y #dns2

change it again to:
search some.newdomain.here
nameserver z.z.z.z #dns3
nameserver a.a.a.a #dns4
reboot again
now it stick to the last update.

Already tried to set /etc/sysconfig/network-scripts/ifcfg-eth0
NM_controlled=no
with no result
other suggestions around the internet suggest also to set in
/etc/sysconfig/network-scripts/ifcfg-eth0
usepeerdns=no
have not tried this but should check if this fixes stuff.

Question: can someone explain me WHY this would help if it does and if
this a valid entry in /etc/sysconfig/network ?
since I don't want to go over all my machines (a couple thousand)
figuring out how many interfaces they have and what their names are to
reconfigure that for each interface (some even suggest this should be
done for lo too).


you should read:
/usr/share/doc/initscripts-*/sysconfig.txt

I would put DNS1 and DNS2 in the ifcfg-* file .


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7 bind-sdb

[Giorgio Bersano]

Hi Robert,
I've no experience with DLZ but IIUC your first question

2015-08-27 22:00 GMT+02:00 Robert Moskowitz :
> This seems to be just a stub with 3 READMEs?
>
> # locate bind-sdb
> /usr/share/doc/bind-sdb-9.9.4
> /usr/share/doc/bind-sdb-9.9.4/INSTALL.ldap
> /usr/share/doc/bind-sdb-9.9.4/README.ldap
> /usr/share/doc/bind-sdb-9.9.4/README.sdb_pgsql
>
> Unless it is putting files elsewhere.
>

# rpm -qf  /usr/share/doc/bind-sdb-9.9.4
bind-sdb-9.9.4-18.el7_1.3.x86_64

(or you could prefer ask to yum)
# yum whatprovides /usr/share/doc/bind-sdb-9.9.4
...
32:bind-sdb-9.9.4-14.el7.x86_64 : BIND server with database backends
and DLZ support
...

# rpm -ql  bind-sdb
/etc/openldap/schema
/etc/openldap/schema/dnszone.schema
/usr/lib/systemd/system/named-sdb.service
/usr/sbin/ldap2zone
/usr/sbin/named-sdb
/usr/sbin/zone2ldap
/usr/sbin/zone2sqlite
/usr/sbin/zonetodb
/usr/share/doc/bind-sdb-9.9.4
/usr/share/doc/bind-sdb-9.9.4/INSTALL.ldap
/usr/share/doc/bind-sdb-9.9.4/README.ldap
/usr/share/doc/bind-sdb-9.9.4/README.sdb_pgsql
/usr/share/man/man1/ldap2zone.1.gz
/usr/share/man/man1/zone2ldap.1.gz
/usr/share/man/man1/zone2sqlite.1.gz
/usr/share/man/man1/zonetodb.1.gz
/usr/share/man/man8/named-sdb.8.gz


HTH,
Giorgio.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] virt-manager with dhcpd running on same machine

[Ron Yorston]

Jerry Geis wrote:
>If I have dhcpd running on my machine,
>and I wish to run virt-manager on the same machine
>How do I do that - its telling me an error for starting the network
>and the error is that DHCPD is already running - port in use.

It seems there's a problem with dnsmasq, which is used by virt-manager:

   https://bugs.centos.org/view.php?id=7884
   https://bugzilla.redhat.com/show_bug.cgi?id=1154953

The workaround mentioned in the bug reports is to downgrade dnsmasq
to the version from CentOS 6.5.

Ron
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] virt-manager with dhcpd running on same machine

[Ashish Yadav]

Hi,

On Fri, Aug 28, 2015 at 2:13 AM, Jerry Geis  wrote:

> If I have dhcpd running on my machine,
> and I wish to run virt-manager on the same machine
> How do I do that - its telling me an error for starting the network
> and the error is that DHCPD is already running - port in use.
>
>
Above problem is due to dnsmasq services which is used by virt-manager.

For virt-manager's networking details can be found at below link,


Please refer below link to configure dnsmasq it.


--Regards
Ashishkumar S. Yadav
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos