On Thu, Mar 19, 2015 at 2:50 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
> I believe the Wordpress was being maintained by Joe Maloney (probably a misspell there), and that the server was set up by DK.
Do you mean Joe Matheny? I'll email him and DK seperately.
We're preparing to migrate the sudoroom.org server sometime soon. The
BAPS wordpress is also sharing that server. It might be easiest - and
maybe even more appropriate - to move BAPS to the omni server ahead of
time and have it live there from now on?
I'd also like to get them an https cert while we're at it.
Who manages the BAPS wordpress? Who's the best person to contact and
coordinate with?
I'm happy to do all the legwork and logistics and will only need help
to reset their DNS at the right time. That and permission or blessings
from all people effected by it would be nice.
Thoughts? :)
On Wed, Mar 11, 2015 at 2:04 AM, Marc Juul <juul(a)labitat.dk> wrote:
> I had a hell of a time getting that to work.
Thank you Marc!!
Did you touch the phone at all? We had phone service with Sonic and
it's not clear whether we could still have a working phone. The old
number 510.858.7155 seems to no longer work.
Also, it looks like you used a personal email address for the account.
How would you feel about using accounts(a)lists.omnicommons.org?
Modem with power cable and 4 filters must be returned in next 30 days.
Instructions and mailing label follow.
Make a great day,
Max Klein ‽ http://notconfusing.com/
---------- Forwarded message ----------
From: <no-reply(a)sonic.net>
Date: Thu, Mar 12, 2015 at 5:00 PM
Subject: Sonic.net Equipment Return
To: isalix(a)gmail.com
Please return the leased Sonic.net equipment kit. Mark your package with
the RMA number, include all components and return the package to
Sonic.net, Inc.
Your RMA number is SRA06DD04
Failure to return the complete kit will result in charges to your credit
card.
$149.00 Pace 5168 Modem/Router
$15.00 Power Supply
$5.00 Pace dual filters (3) and DSL splitter (1)
You can print your return label by following the link below. Be sure to
include your RMA number and deliver the package to any UPS facility,
drop box or driver.
https://www.ups.com/u.a/L.class?8RG5FOQt%252F0ZYJQWWjHrWRuZNw%252Fa%252Fe9u…
If you have any questions, please contact Customer Support at
1-888-766-4233 from 6am-11pm, Monday-Friday and 8am-10pm, Saturday and
Sunday.
Sonic.net, Inc.
2260 Apollo Way
Santa Rosa, CA 95407
I had a hell of a time getting that to work.
The new DSL modem / router is now operating as a bridge, meaning that it's
just a dumb modem and not doing any routing. It has a management IP of
10.0.0.1 but of course it's on the internet-facing side of our gateway so
the easiest way to get to that is to plug into the dsl modem/router with
ethernet, set your own IP to e.g. 10.0.0.2 and open a web browser to
10.0.0.1
The login info is in /root/passwords on space.local
The wifi on the dsl modem/router has been turned off.
I don't know if we have a static IP from LMI, but this is our IP for now:
142.254.119.218
The LMI DCHP server was willing to give out one IP for the modem/router,
and then one IP to my laptop during testing, and then it would not give out
any more IP leases to any other machines even after explicitly releasing
the lease from my laptop. Setting a static IP in the same range didn't even
work. I had to change the MAC address on the eth1 network interface on
space.local to my laptop's ethernet MAC address. I put that in
/etc/network/interfaces for now, but I'll call up LMI when I have a moment
and see if we can sort out a static IP.
Since the dsl modem/router allows backing up and restoring configurations,
I put the configuration prior to any fiddling by me in:
/root/dsl_modem_configs/original.conf
and the configuration as it is as I'm writing this email in:
/root/dsl_modem_configs/bridge_mode_working_march_11th_2015.conf
--
marc/juul
On Tue, Mar 10, 2015 at 2:33 AM, Marc Juul <juul(a)labitat.dk> wrote:
> Anyone know anything about this? Looks suspiciously like someone gained some
> level of access to the server.
It just means someone tried to use sudo and failed.
I switched us to the new LMI connection. Unfortunately I didn't have my
laptop with me so I couldn't reconfigure the sudo server to work with the
new connection. For now I simply bypassed the server. Will fix it tomorrow.
Also, who should I talk to about cancelling our previous connection?
Anyone know anything about this? Looks suspiciously like someone gained
some level of access to the server.
On Mon, Mar 9, 2015 at 7:49 PM, <web-ooo(a)omnicommons.org> wrote:
> omnicommons.org : Mar 9 19:49:29 : web-ooo : user NOT in sudoers ;
> TTY=pts/6 ; PWD=/home/web-ooo ; USER=root ; COMMAND=/bin/su jenny
>
> _______________________________________________
> sysadmins mailing list
> sysadmins(a)lists.omnicommons.org
> https://omnicommons.org/lists/listinfo/sysadmins
>
On Thu, Mar 5, 2015 at 11:34 AM, yar <yardenack(a)gmail.com> wrote:
> It's at maybe the worst possible time (6pm tonight) but there's
> nothing we can do about it. We'll try to make it as quick & smooth as
> possible.
all done!
It's at maybe the worst possible time (6pm tonight) but there's
nothing we can do about it. We'll try to make it as quick & smooth as
possible.
---------- Forwarded message ----------
From: <support(a)linode.com>
Date: Sun, Mar 1, 2015 at 11:35 AM
Subject: Linode Support Ticket 4254236 - Critical Xen Maintenance /
Reboot Schedule
Hello,
Linode recently received several Xen Security Advisories (XSAs) that
require us to perform updates to our host servers. In order to apply
the updates, hosts and the Linodes running on them must be rebooted.
The XSAs will be publicly released by the Xen project team on March
10th, therefore we must complete the updates before that date.
These updates are required to protect the security and safe operations
of not only our infrastructure, but yours as well. We understand that
a disruption with such limited notice is inconvenient, and we hope you
understand that these measures are warranted due to the severity of
the XSAs.
Your Linodes have been assigned a maintenance window in which a reboot
will occur. These times are listed within the Linode Manager[1] in the
timezone set in your user's My Profile[2]. Your schedule in UTC
timezone is as follows:
* 2015-03-06 2:00:00 AM UTC - sudoserver
During the maintenance window Linode instances will be cleanly shut
down while we perform the updates. Your Linode will be inaccessible
during this time. A two-hour window is allocated, however the actual
downtime can be much less. After the maintenance, each Linode will
then be booted. See our Reboot Survival Guide[3] for tips and hints on
configuring and testing that your Linode services boot properly after
the maintenance.
Unfortunately, due the logistical demands of this effort, your
assigned windows are not changeable and the host reboots are
mandatory.
For general information, please see our status post:
<http://status.linode.com/incidents/2dyvn29ds5mz>
Please let us know if there is anything we can do to assist.
[1] <https://manager.linode.com/linodes>
[2] <https://manager.linode.com/profile>
[3] <https://www.linode.com/docs/uptime/reboot-survival-guide>
-Linode
