pdxdevops.org site is rendering the apache default

21 views
Skip to first unread message

Greg Buehler

unread,
Mar 9, 2016, 4:58:31 PM3/9/16
to pdxdevops
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

David Gibbons

unread,
Mar 9, 2016, 5:04:58 PM3/9/16
to pdxd...@googlegroups.com
Did someone update the apache modules in configuration management?

On Wed, Mar 9, 2016 at 11:57 AM, Greg Buehler <gregory....@gmail.com> wrote:
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Spencer Krum

unread,
Mar 9, 2016, 5:06:14 PM3/9/16
to pdxd...@googlegroups.com
Hi Greg,

Ya, this is a known issue and has been going on for a couple weeks now. The stumptown syndicate runs the website, and I've not been able to get in touch with anyone over there to fix it.

Thanks,
Spencer

On Wed, Mar 9, 2016 at 11:57 AM, Greg Buehler <gregory....@gmail.com> wrote:
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

Reid Beels

unread,
Mar 9, 2016, 6:17:40 PM3/9/16
to pdxdevops
Hi All,

Sorry for not chiming in on this earlier — I've been trying to find time to do a bit of triage. The pdxdevops site got hit pretty heavily by spambots a couple of weeks ago. Spencer emailed me about the frontpage missing its content, and I logged in and restored it to an earlier version. Then, last week, we noticed that the load on the server hosting the site was spiking from Dokuwiki running reindexing tasks and that its outgoing mail queues were very full. There was a pretty constant stream of automated edits going on so, one of our other admins disabled the vhost.

I just reenabled the vhost, where all of the wiki data is safe and sound — albeit mixed with thousands of spam pages. I've restored the front page and locked things down so that user registration is disabled and only admins can make changes. Let me know if anyone needs admin access there and I can grant it. Going forward, given the frequency of bot attacks on this sort of open wiki, I'm not sure this is the best option for the pdxdevops site. We're currently looking at moving the pdxruby site from dokuwiki to a static site backed by a github repo, and it may make sense for pdxdevops to explore a similar path.

Best,
Reid



On Wednesday, March 9, 2016 at 11:06:14 PM UTC+1, Spencer Krum wrote:
Hi Greg,

Ya, this is a known issue and has been going on for a couple weeks now. The stumptown syndicate runs the website, and I've not been able to get in touch with anyone over there to fix it.

Thanks,
Spencer
On Wed, Mar 9, 2016 at 11:57 AM, Greg Buehler <gregory....@gmail.com> wrote:
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

Spencer Krum

unread,
Mar 9, 2016, 6:33:03 PM3/9/16
to pdxd...@googlegroups.com
Hi Reid,

Thanks for jumping in. I agree that a static site is probably the way forward for us. Are you expecting to host the static site via pages.github or on the syndicate server?

Thanks,
Spencer

To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

Reid Beels

unread,
Mar 9, 2016, 6:39:34 PM3/9/16
to pdxdevops
Either way — I think that hosting it on GitHub pages probably makes the most sense, since you don't have to deal with a separate deployment step and group members can still make updates after meetings, much in the same way they'd update the current wiki, but just submitting pull requests. 

Reid


On Thursday, March 10, 2016 at 12:33:03 AM UTC+1, Spencer Krum wrote:
Hi Reid,

Thanks for jumping in. I agree that a static site is probably the way forward for us. Are you expecting to host the static site via pages.github or on the syndicate server?

Thanks,
Spencer
On Wed, Mar 9, 2016 at 3:17 PM, Reid Beels <rei...@gmail.com> wrote:
Hi All,

Sorry for not chiming in on this earlier — I've been trying to find time to do a bit of triage. The pdxdevops site got hit pretty heavily by spambots a couple of weeks ago. Spencer emailed me about the frontpage missing its content, and I logged in and restored it to an earlier version. Then, last week, we noticed that the load on the server hosting the site was spiking from Dokuwiki running reindexing tasks and that its outgoing mail queues were very full. There was a pretty constant stream of automated edits going on so, one of our other admins disabled the vhost.

I just reenabled the vhost, where all of the wiki data is safe and sound — albeit mixed with thousands of spam pages. I've restored the front page and locked things down so that user registration is disabled and only admins can make changes. Let me know if anyone needs admin access there and I can grant it. Going forward, given the frequency of bot attacks on this sort of open wiki, I'm not sure this is the best option for the pdxdevops site. We're currently looking at moving the pdxruby site from dokuwiki to a static site backed by a github repo, and it may make sense for pdxdevops to explore a similar path.

Best,
Reid


On Wednesday, March 9, 2016 at 11:06:14 PM UTC+1, Spencer Krum wrote:
Hi Greg,

Ya, this is a known issue and has been going on for a couple weeks now. The stumptown syndicate runs the website, and I've not been able to get in touch with anyone over there to fix it.

Thanks,
Spencer
On Wed, Mar 9, 2016 at 11:57 AM, Greg Buehler <gregory....@gmail.com> wrote:
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

Spencer Krum

unread,
Mar 10, 2016, 1:52:48 PM3/10/16
to pdxd...@googlegroups.com
I've set up http://nibalizer.github.io/pdxdevops.org/ to be hosted out of github. And given access to write to that repository to Nick and Alice. I've also set up the CNAME file so that it can serve pdxdevops.org.

The DNS for this site is also in a strange spot. I think that currently Puppet Labs registers, pays for, and administrates the domain. Thanks Puppet Labs! But I think they've said a few times that they'd like to not be doing that going forward. I think we've tried a few times to move that to the syndicate. I'm fine with it going to the syndicate (the devops org can pay the syndicate's registration fees) or the DNS can just come and live in my personal account and I'll move it on to the next organizer when I move out of a leadership role.


On Wed, Mar 9, 2016 at 3:39 PM, Reid Beels <rei...@gmail.com> wrote:
Either way — I think that hosting it on GitHub pages probably makes the most sense, since you don't have to deal with a separate deployment step and group members can still make updates after meetings, much in the same way they'd update the current wiki, but just submitting pull requests. 

Reid


On Thursday, March 10, 2016 at 12:33:03 AM UTC+1, Spencer Krum wrote:
Hi Reid,

Thanks for jumping in. I agree that a static site is probably the way forward for us. Are you expecting to host the static site via pages.github or on the syndicate server?

Thanks,
Spencer
On Wed, Mar 9, 2016 at 3:17 PM, Reid Beels <rei...@gmail.com> wrote:
Hi All,

Sorry for not chiming in on this earlier — I've been trying to find time to do a bit of triage. The pdxdevops site got hit pretty heavily by spambots a couple of weeks ago. Spencer emailed me about the frontpage missing its content, and I logged in and restored it to an earlier version. Then, last week, we noticed that the load on the server hosting the site was spiking from Dokuwiki running reindexing tasks and that its outgoing mail queues were very full. There was a pretty constant stream of automated edits going on so, one of our other admins disabled the vhost.

I just reenabled the vhost, where all of the wiki data is safe and sound — albeit mixed with thousands of spam pages. I've restored the front page and locked things down so that user registration is disabled and only admins can make changes. Let me know if anyone needs admin access there and I can grant it. Going forward, given the frequency of bot attacks on this sort of open wiki, I'm not sure this is the best option for the pdxdevops site. We're currently looking at moving the pdxruby site from dokuwiki to a static site backed by a github repo, and it may make sense for pdxdevops to explore a similar path.

Best,
Reid


On Wednesday, March 9, 2016 at 11:06:14 PM UTC+1, Spencer Krum wrote:
Hi Greg,

Ya, this is a known issue and has been going on for a couple weeks now. The stumptown syndicate runs the website, and I've not been able to get in touch with anyone over there to fix it.

Thanks,
Spencer
On Wed, Mar 9, 2016 at 11:57 AM, Greg Buehler <gregory....@gmail.com> wrote:
It looks like there is a configuration issue with the pdxdevops.org web server. I'm seeing the apache default page.

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

--
You received this message because you are subscribed to the Google Groups "pdxdevops" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdxdevops+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Spencer Krum
(619)-980-7820

Nigel Kersten

unread,
Mar 14, 2016, 5:05:17 PM3/14/16
to pdxd...@googlegroups.com

On Fri, Mar 11, 2016 at 5:52 AM, Spencer Krum <krum.s...@gmail.com> wrote:
The DNS for this site is also in a strange spot. I think that currently Puppet Labs registers, pays for, and administrates the domain. Thanks Puppet Labs! But I think they've said a few times that they'd like to not be doing that going forward. I think we've tried a few times to move that to the syndicate. I'm fine with it going to the syndicate (the devops org can pay the syndicate's registration fees) or the DNS can just come and live in my personal account and I'll move it on to the next organizer when I move out of a leadership role.

:) We've been happy to do it, but it does seem like it's better for the syndicate to administer it and not be reliant upon us.

If money is a problem for the group, I'm sure a bunch of us who work at companies in town can work out something.

Is anything in particular blocking the transfer? My memory is that each time we've tried to do it, the transfer request we've initiated from our side has expired due to inaction... but I could be wrong.


Reply all
Reply to author
Forward
0 new messages