Evergreen ILS Website

IRC log for #evergreen, 2017-01-23

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
01:26 htcoder joined #evergreen
01:31 htcoder left #evergreen
02:26 bmills joined #evergreen
05:02 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
07:10 rjackson_isl joined #evergreen
07:15 JBoyer joined #evergreen
07:20 agoben joined #evergreen
08:15 rlefaive joined #evergreen
08:24 collum joined #evergreen
08:38 mmorgan joined #evergreen
08:51 mdriscoll joined #evergreen
08:52 bos20k joined #evergreen
09:05 yboston joined #evergreen
09:11 collum_ joined #evergreen
09:26 Dyrcona joined #evergreen
09:28 maryj joined #evergreen
09:30 collum joined #evergreen
09:36 kmlussier joined #evergreen
09:38 kmlussier Good morning #evergreen!
09:38 kmlussier @coffee [someone]
09:38 * pinesol_green brews and pours a cup of Kenya Githiru, and sends it sliding down the bar to rashma
09:38 kmlussier @tea [someone]
09:38 * pinesol_green brews and pours a pot of Keemun Full Leaf Tea, and sends it sliding down the bar to jonadab (http://ratetea.com/tea/fooj​oy/keemun-full-leaf/6686/)
09:44 mmorgan kmlussier: Good Morning!
10:00 bshum @weather hkg
10:00 pinesol_green bshum: Hong Kong International, China :: Clear :: 63F/17C | Monday: Partly cloudy. Lows overnight in the low 60s. Monday Night: A few clouds. Low around 60F. Winds E at 15 to 25 mph.
10:01 Dyrcona @weather
10:01 pinesol_green Dyrcona: Methuen, MA :: Overcast :: 33F/1C | Wind Chill: 23F/-5C | Monday: Variable clouds with snow showers that will mix with rain showers later. Temps nearly steady in the mid 30s. Winds ENE at 15 to 25 mph. Chance of precip 50%. Winds could occasionally gust over 40 mph. Monday Night: Periods of rain and snow this evening will turn to rain overnight. Windy. Some sleet may (1 more message)
10:02 mmorgan1 joined #evergreen
10:22 kmlussier joined #evergreen
10:47 mmorgan joined #evergreen
10:57 Christineb joined #evergreen
11:06 Dyrcona Nothing is simple with ejabberd.
11:08 JBoyer Nothing is simple once it touches a network.
11:11 Dyrcona Well, in setting up the new VMs, the host name (and erlang node) have changed.
11:11 Dyrcona Following the instructions for fixing that, doesn't work.
11:11 Dyrcona https://docs.ejabberd.im/admin/guide​/managing/#change-computer-hostname
11:12 Dyrcona I wonder if I can just dpkg-reconfigure and configure it by hand again?
11:14 Dyrcona Nope.
11:16 JBoyer Since we only use 4 accounts, the way I've seen this handled in the past is to stop ejabberd, wipe out all of the Mnesia stuff (/var/lib/ejabberd/*), re-start it and then re-register the accounts.
11:16 JBoyer That obviously wouldn't be the way to go if you were actually running a chat server with it, but for what we do it's not a big deal.
11:19 berick Dyrcona: setting ERLANG_NODE to the old hostname in /etc/default/ejabberd has worked for me several times
11:19 berick ERLANG_NODE=ejabberd@old-host-name
11:20 Dyrcona berick: I'll give that a shot in a minute. I've tried --node ejabberd@old-hostname but it doesn't start that way with ejabberdctl
11:23 Dyrcona Nope. Doesn't help. Trying to start ejabberd with the old node name says, nodedown...
11:23 berick did you kill epmd?
11:23 Dyrcona Nothing in Google has so far been helpful, just more of the same, do these 10 steps, and step 1 fails.
11:24 berick i usually have to manually kill some jabber/erlang-related stuff by hand to reset it all.  or reboot.
11:24 pinesol_green [evergreen|Kathy Lussier] Docs: Add browser requirements for running the web client - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=c6935c0>
11:24 Dyrcona yeah. beam.smp seems to be lieft running. I killed that.
11:25 Dyrcona I wish I could just blow out /var/lib/ejabberd and have it recreated...
11:26 Dyrcona I didn't anticipate this.
11:26 csharp I've done it before, but it was messy and I don't remember the steps - I think you have to update the erlang internal db
11:26 csharp yeah mnesia
11:28 csharp the second comment on https://www.ejabberd.im/node/24841 is similar to what I did long ago
11:29 csharp oh wait - that assumes you haven't changed the name yet
11:30 csharp no it doesn't - sorry - case of the Mondays over here
11:30 khuckins_ joined #evergreen
11:31 Dyrcona Yeap: ejabberdctl --node $OLDNODE start
11:31 Dyrcona Step 1: Blows up for me.
11:32 Dyrcona Failed RPC connection to the node ejabberd@debian7: nodedown
11:32 Dyrcona Googling the message finds nothing useful so far.
11:32 csharp I really wish I'd documented what I did :-/ I was in a similar loop
11:35 Dyrcona Copying the old config file into place doesn't help, yet.
11:35 Dyrcona Maybe epmd or some crap is still running.
11:35 Dyrcona erlang-- # Too complicated.
11:36 Dyrcona I'll bet I have to change the hostname.....
11:38 Dyrcona Nope. Doesn't help.
11:39 Dyrcona So, I guess I can force purge ejabberd and reinstall it.
11:40 * jeff scrolls up
11:42 berick csharp: hey, did you apply that hold targeter fix?  any word on that?
11:42 jeff my usual process with ejabberd on systems where I expect the hostname to change often is to set ERLANG_NODE to ejabberd@localhost in /etc/default/ejabberd -- in those situations there's also no cross-server ejabberd communication.
11:43 berick jeff++ # proactive
11:44 jeff if the daemon has been started before I preseed that value, I usually: stop ejabberd, remove the contents of /var/lib/ejabberd (including .erlang.cookie), and then start it back up again. This is easier if you get to it before the hostname changes.
11:48 Dyrcona jeff: /var/lib/ejabberd will be automagically fixed?
11:53 Dyrcona Trouble with all the fiddling around is all of the cleanup.
11:54 Dyrcona jeff++
11:55 JBoyer I actually played with Erlang a little bit a few years ago, and I'll say this isn't the language's fault, it's all on ejabberd or Mnesia specifically. That doesn't help now, but at least not every Erlang project is a huge pain in this regard.
11:55 jeff Dyrcona: yes, in my experience with Debian wheezy and jessie, the removed contents of /var/lib/ejabberd will be re-created when ejabberd starts.
11:56 Dyrcona Yeah, since I had not even registered users, yet, nothing useful was lost, either.
11:58 jeff (you do end up needing to re-create users if you'd done that already)
12:04 csharp berick: yes, and it appears to have solved the problem
12:05 berick csharp: yay
12:05 berick thanks
12:07 Dyrcona jeff: Yeah. I had not registered the users, yet.
12:08 Dyrcona I was at that point when I noticed the trouble. :)
12:08 jeff heh
12:09 jeff if the hostname has changed already, it's trickier, but usually only in that you likely need to manually kill ejabberd/erlang processes, as ejabberdctl and initscripts / systemd may no longer be able to stop them.
12:10 Dyrcona Well, since I made a model vm for multiple roles and only 1 of those runs ejabberd, I turned it off on the model.
12:13 Dyrcona Next time, I'll do better. :)
12:14 jihpringle joined #evergreen
12:16 csharp berick: if we get through this week without any reported problems, I think we can consider it all good
12:16 * dbs got a Xenial VM up and running with opensrf & evergreen master last night, no problems. yay. but I didn't bother with webby this time around
12:18 berick csharp: *nod* very cool.  i'll keep my eyes peeled.
12:18 * jeff scrolls through the list of conference program proposals
12:44 sandbergja joined #evergreen
13:05 brahmina joined #evergreen
13:35 mmorgan joined #evergreen
14:24 Dyrcona It's alive!
14:25 Dyrcona My VM replacement for brick 3 has been running for 20+ minutes, processing requests, and logging to the log server.
14:25 JBoyer Dyrcona++
14:25 Dyrcona Now, to finish the vm for sip3.
14:26 jeff "SIP 3.0" or "third SIP server"?
14:27 jeff (or, of course... something else entirely)
14:27 Dyrcona Third SIP server. We have 4.
14:28 Dyrcona Basically, we're upgrading server hardware.
14:28 Dyrcona We're replacing 4 physical servers with 1 that runs 4 VMs.
14:28 Dyrcona Doing that for each of 5 bricks.
14:29 Dyrcona We did brick #3 first, because one of its drone servers has been out of commission.
14:31 Dyrcona It was doing all right with only 1 drone server, too.
14:32 Dyrcona Y'know. It might have been a good idea to preseed the VMs with ~opensrf/.ssh/authorized_keys. :)
14:34 jeff or let ansible maintain them. :-)
14:35 Dyrcona Maybe some day.
14:59 Dyrcona So, just checking on things and I've got a cstore drone using 100% cpu with a time over 276:24.... Think it would be OK to kill it?
15:08 khuckins_ joined #evergreen
15:12 Dyrcona Seeing as that cstore last shows up in the logs about 4 hours ago, I think it would be safe to kill it.
15:19 Dyrcona And, hey! The load on that drone server is dropping. :)
15:33 collum joined #evergreen
16:17 mllewellyn joined #evergreen
16:39 mllewellyn left #evergreen
16:58 jlundgren left #evergreen
17:02 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
17:08 mmorgan left #evergreen
21:09 dcook joined #evergreen
22:07 dcook joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat