Monday, 2014-10-13

*** nowen (~nowen@99-174-92-191.lightspeed.tukrga.sbcglobal.net) has joined #wikid13:18
*** Troy (47c4f5b0@gateway/web/freenode/ip.71.196.245.176) has joined #wikid14:22
nowenhey Troy14:22
TroyHey Nick.. good morning14:22
nowenGood morning14:22
Troyyou'll be happy to hear that tomorrow is the day we upgrade!14:23
Troyfinally14:23
Troyi have a quick question before I do the upgrade tomorrow14:23
TroyDuring the process I will have to regenerate the WiKID certificate chain.. Would it be possible to create the cert chain on our upgraded WiKID lab server ahead of time then copy the /private folder over to production after the upgrade?14:23
Troyof course I would backup the lab certs first14:24
nowenYes, that should work fine.14:25
nowengood idea, should make it much fater14:25
nowenfaster14:25
Troyok.. that's what I thought.. should work as long as the cert hostnames match up14:26
nowenyep14:26
Troythat good news. that should save me a bit of time tomorrow..14:26
Troyalso, I think the db sync connection timeout could be a result of the alarm setting in the wikid.pl set too low14:27
Troyi think it is set to 30 .. which that time could vary depending on the system14:28
nowenhmm, ok. interesting14:29
nowenis there any clock drift between the two?14:30
Troydo you see any problem increasing that time to 60 for the sub Master_cp (sync function)14:30
nowennot really14:30
Troysince we are pushing the entire db (400-800MB) over the WAN.. I don't think 30 seconds is quite long enough14:30
nowenlol, no, I guess not ;-)14:30
Troythe db size between the master and slave seemsto get out of sync almost weekly.. i'm wondering if there is anything else we can adjust to keep these in sync better14:32
Troythe only way I know to get them back synced is to shut both servers down and re-sync the entire db over and start them up in replication14:32
Troyi know our WAN speed can be flaky at times. but i'm hoping we can find a way to keep them better synced without having to re-copy each week.. any suggestions would be appreciated14:34
Troythe SSH settings are optimized (GSSAPIAuthentication no, UseDNS no)14:35
nowenok, I'll chew on it14:39
nowenboth are running NTP?  We have seen issues where clock drift causes issues on virtual instances14:41
Troyyes.. both are on NTP14:47
Troyi'll double check the clock though14:47
nowenok14:50
nowenbrb15:10
*** nowen has parted #wikid (None)15:11
*** nowen (~nowen@99-174-92-191.lightspeed.tukrga.sbcglobal.net) has joined #wikid15:16
*** nowen1 (~nowen@99-174-92-191.lightspeed.tukrga.sbcglobal.net) has joined #wikid17:38
*** nowen has quit (Ping timeout: 260 seconds)17:39
*** nowen1 is now known as nowen17:40
*** WiKIDLogBot (~WiKIDLogB@ec2-54-83-0-181.compute-1.amazonaws.com) has joined #wikid19:53
sinisalo.freenode.netTopic for #wikid is: two-factor authentication.  If no one is here, you can try the forums: http://www.wikidsystems.com/support/support/wikid-forums.  Please lurk around - your question may not be answer immediately. This channel is logged:  http://www.wikidsystems.com/webdemo/irclogs/index.html.19:53
sinisalo.freenode.netUsers on #wikid: WiKIDLogBot @nowen luntwrap coolacid joevano @ChanServ19:53
*** Troy (47c4f5b0@gateway/web/freenode/ip.71.196.245.176) has joined #wikid20:18
TroyHey Nick20:19
nowenhey20:19
TroyI won't be invalidating my current production intermediate cert by creating a new intermediate CA from my lab server?20:20
nowenno20:20
Troyso I can submit a new CSR with the same production host in the lab?20:21
nowenyeah, you do have to have a unique DN, but minor changes is all you need20:21
Troyok.. that's good.. i didn't want to break anything by going through the cert chain process20:22
nowennah, we can handle it20:22
nowengot to go.  email me if you need me21:01
*** nowen has quit (Quit: Leaving.)21:01
*** Troy has quit (Quit: Page closed)21:25

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!