Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2014-05-09

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:24 rmoe joined #fuel
00:26 IlyaE joined #fuel
01:15 rmoe joined #fuel
01:28 xarses joined #fuel
02:29 xarses joined #fuel
02:34 IlyaE joined #fuel
02:55 IlyaE joined #fuel
03:41 rmoe joined #fuel
04:17 IlyaE joined #fuel
04:34 Ch00k joined #fuel
05:12 IlyaE joined #fuel
06:05 IlyaE joined #fuel
06:59 IlyaE joined #fuel
07:19 al_ex joined #fuel
08:23 e0ne joined #fuel
08:40 topochan joined #fuel
08:48 e0ne joined #fuel
10:07 e0ne joined #fuel
10:17 Ch00k joined #fuel
11:00 e0ne joined #fuel
11:19 e0ne joined #fuel
11:38 topochan joined #fuel
12:02 TVR_ Hey MiroslavAnashkin, could I bother you for a question? I set my floating IP to an instance and I cannot reach it externally... I changed my  Access and Security to allow all ICMP, TCP and UDP so it shouldn't be there... I  initially could ping out to the real world (4.2.2.1) but traceroute showed going to my gateway for public was going out the instances gateway rather than out the floating IP... so I admin down the network:router_gatew
12:02 TVR_ utside access at all.
12:09 TVR_ I have tried bouncing the router virtual interfaces by ip netns exec qrouter-964cd4f1-ab18-46fb-a0bc-b2c1298ce8ba ip link set dev qr-2bc1a257-b9 down and then up as well
12:10 TVR_ both interfaces on the router are in state UNKNOWN
12:13 TVR_ I can ping from the instance the instance gateway, and the other side of the virtual router's IP... but cannot ping the routers gateway
12:16 TVR_ externally I can ping the virtual routers gateway... so if I can simply get the virtual router to start handing traffic to it's gateway.. I should be good
12:37 tatyana joined #fuel
12:53 mattymo|home joined #fuel
14:04 jobewan joined #fuel
14:18 topochan joined #fuel
15:38 blahRus joined #fuel
15:54 IlyaE joined #fuel
15:58 TAJ joined #fuel
16:10 rmoe joined #fuel
16:40 Bomfunk joined #fuel
16:52 blahRus joined #fuel
16:53 xarses joined #fuel
17:17 xarses joined #fuel
17:19 albionandrew joined #fuel
17:19 jaypipes joined #fuel
17:19 albionandrew I have a problem where crm status shows p_mysql failing to start. Is crm resource restart p_mysql not the correct way to restart it?
17:20 albionandrew It just fails on 1 node
17:20 angdraug joined #fuel
17:36 xarses joined #fuel
17:43 IlyaE joined #fuel
17:49 mutex albionandrew: what is the error message, I have a similar one
17:50 albionandrew mutex I see this in the logs ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
17:50 albionandrew and from crm status p_mysql_monitor_60000 …..call=344, rc=7, status=complete): not running
17:53 mutex you are restarting it the right way
17:53 mutex but there may be some other problem
17:53 mutex did you check the mysqld logs on the fuel master node ?
17:53 mutex they are in /var/log/remote/<node>/mysqld.log
17:53 mutex that might give you some insights
17:57 albionandrew Thats where that error comes form the remote logs. I restarted or tried to using “ crm resource restart p_mysql”
17:58 mutex yeah that only works sometimes I have found
17:59 mutex in fact my DB is sick right now, and restarting via crm does not bring it back
18:01 mutex it is interesting
18:01 mutex when I ask mysql what the status of the cluster is, the nodes all say they are 'CONNECTED' but nobody is primary
18:34 mutex looksl ike I just don't have a primary in my cluster
18:37 mutex I think I need to run mysql-wss promote on one of my nodes so that I can start the cluster
18:37 mutex but it does not seem to work
19:22 IlyaE joined #fuel
20:08 e0ne joined #fuel
21:03 IlyaE joined #fuel
21:17 aglarendil mutex: mysql-wss is not multistate script
21:17 aglarendil it works only as start/stop right now
22:19 IlyaE joined #fuel
22:36 mutex aglarendil: yeah, I ended up turning off the cluster then designating one as the master

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary