Re: [Vyatta-users] Unable to login, solved by reboot
Sounds like the right call. Cheers, -- Dave Roberts -Original Message- From: Jostein Martinsen-Jones [EMAIL PROTECTED] To: Dave Roberts [EMAIL PROTECTED] Cc: Justin Fletcher [EMAIL PROTECTED]; vyatta-users [EMAIL PROTECTED] Sent: 2/2/2008 5:53 AM Subject: Re: [Vyatta-users] Unable to login, solved by reboot Gisch, sounds like i'll stick to the stable release until Glendale is stable. We are going to have customer systems behind the router, and the customers doesn't appreciate downtime at all. 2008/1/31, Dave Roberts [EMAIL PROTECTED]: Glendale probably hasn't had enough widespread alpha testing to know for sure, but having said that, I think the general consensus from people at Vyatta as well as some other comments we have gotten from outside is that it feels a lot more stable. By stable, I specifically mean a lot less random behavior. Generally, with Glendale things either work or they don't. Now, having said that, there is a *lot* of stuff that doesn't work (a lot of loose ends, rough edges, etc.), but if you don't need those features, then the stuff that does work seems to work well. Put another way, if you can configure it and you test it and it works, it will probably keep working well. Vyatta currently uses Glendale everyday in our production network, for instance, and we don't see crashes. So... If servers that soon will go live means an intranet, internal company web site that can afford to be down for a few hours to upgrade to Glendale Alpha 2 and Beta in a month or two and your company won't go out of business if there is a problem, then I'd probably install Glendale Alpha 1 and I think you would probably be happy with it. If servers that soon will go live refer to multi-million dollar, revenue-generating, business-critical systems that have limited maintenance windows, etc., where you would be fired outright if things suddenly stopped working, then I definitely wouldn't do it. It's simply too risky at this point and at a minimum you'll want to upgrade to Alpha 2 and/or Beta when those become available, which would require possibly large amounts of downtime. But if you decide to go for it, we'd be very interested in any feedback you have. ;-) -- Dave -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Jostein Martinsen-Jones *Sent:* Wednesday, January 30, 2008 3:06 PM *To:* Justin Fletcher *Cc:* vyatta-users *Subject:* Re: [Vyatta-users] Unable to login, solved by reboot How production ready are Glendale. I'm using vyatta as router/firewall in front of a couple of servers that soon will go live... Since it's alpha, do you think I should do it? Just printed the whole manual... 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: Maybe . . . However, much of this has been resolved with associated changes in Glendale. Give Alpha 1 a try - I doubt you'll see it there :-) Best, Justin On Jan 30, 2008 12:43 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: But i feel that the only reason I didn't have to reboot is luck :( Maybe next time i'm unable to login with any account? 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
Maybe . . . However, much of this has been resolved with associated changes in Glendale. Give Alpha 1 a try - I doubt you'll see it there :-) Best, Justin On Jan 30, 2008 12:43 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: But i feel that the only reason I didn't have to reboot is luck :( Maybe next time i'm unable to login with any account? 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
How production ready are Glendale. I'm using vyatta as router/firewall in front of a couple of servers that soon will go live... Since it's alpha, do you think I should do it? Just printed the whole manual... 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: Maybe . . . However, much of this has been resolved with associated changes in Glendale. Give Alpha 1 a try - I doubt you'll see it there :-) Best, Justin On Jan 30, 2008 12:43 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: But i feel that the only reason I didn't have to reboot is luck :( Maybe next time i'm unable to login with any account? 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
Personally, I'd use it to take advantage of major changes and fixes, and I'm running it to access all 40 lab systems - but that's me :-) It still needs more polish, and there's a good chance you'll find things that aren't perfect (or maybe even a bug or two), and you'll have to re-enter and/or substantially modify your existing configuration. If you want to be cautious and prudent, review the bugs in the bug list, and try it on a backup system. Best, Justin On Jan 30, 2008 3:06 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: How production ready are Glendale. I'm using vyatta as router/firewall in front of a couple of servers that soon will go live... Since it's alpha, do you think I should do it? Just printed the whole manual... 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: Maybe . . . However, much of this has been resolved with associated changes in Glendale. Give Alpha 1 a try - I doubt you'll see it there :-) Best, Justin On Jan 30, 2008 12:43 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: But i feel that the only reason I didn't have to reboot is luck :( Maybe next time i'm unable to login with any account? 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
Glendale probably hasn't had enough widespread alpha testing to know for sure, but having said that, I think the general consensus from people at Vyatta as well as some other comments we have gotten from outside is that it feels a lot more stable. By stable, I specifically mean a lot less random behavior. Generally, with Glendale things either work or they don't. Now, having said that, there is a *lot* of stuff that doesn't work (a lot of loose ends, rough edges, etc.), but if you don't need those features, then the stuff that does work seems to work well. Put another way, if you can configure it and you test it and it works, it will probably keep working well. Vyatta currently uses Glendale everyday in our production network, for instance, and we don't see crashes. So... If servers that soon will go live means an intranet, internal company web site that can afford to be down for a few hours to upgrade to Glendale Alpha 2 and Beta in a month or two and your company won't go out of business if there is a problem, then I'd probably install Glendale Alpha 1 and I think you would probably be happy with it. If servers that soon will go live refer to multi-million dollar, revenue-generating, business-critical systems that have limited maintenance windows, etc., where you would be fired outright if things suddenly stopped working, then I definitely wouldn't do it. It's simply too risky at this point and at a minimum you'll want to upgrade to Alpha 2 and/or Beta when those become available, which would require possibly large amounts of downtime. But if you decide to go for it, we'd be very interested in any feedback you have. ;-) -- Dave _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jostein Martinsen-Jones Sent: Wednesday, January 30, 2008 3:06 PM To: Justin Fletcher Cc: vyatta-users Subject: Re: [Vyatta-users] Unable to login, solved by reboot How production ready are Glendale. I'm using vyatta as router/firewall in front of a couple of servers that soon will go live... Since it's alpha, do you think I should do it? Just printed the whole manual... 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: Maybe . . . However, much of this has been resolved with associated changes in Glendale. Give Alpha 1 a try - I doubt you'll see it there :-) Best, Justin On Jan 30, 2008 12:43 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: But i feel that the only reason I didn't have to reboot is luck :( Maybe next time i'm unable to login with any account? 2008/1/30, Justin Fletcher [EMAIL PROTECTED]: As you can see, nothing jumps out in the log. A detailed search may turn up more information; otherwise, at least you've got a work-around :-) Justin On Jan 29, 2008 2:48 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Re: [Vyatta-users] Unable to login, solved by reboot
Log result attached. I managed to login if I changed the passwords for my troubled users. Somethimes the encrypted-password didn't get encrypted. 2008/1/29, Justin Fletcher [EMAIL PROTECTED]: Give show log | match ERROR a try. Justin On Jan 29, 2008 2:00 PM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: I have this problem again. Now i was able to login to a user account I created, but unable to view logfiles since im in xorpsh. 2008/1/28, Justin Fletcher [EMAIL PROTECTED]: Anything untoward in the log files? Justin On Jan 28, 2008 7:29 AM, Jostein Martinsen-Jones [EMAIL PROTECTED] wrote: Today I had a wierd experience with Vyatta. I was unable to login on any account. Did a reboot, then everything was normal. What is going on? ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users ;; This buffer is for notes you don't want to save, and for Lisp evaluation. ;; If you want to create a file, visit that file with C-x C-f, ;; then enter the text in that file's own buffer. show log | match ERROR Jan 27 14:20:41 localhost xorp_rtrmgr: [ 2008/01/27 15:20:41 ERROR xorp_rtrmgr:3758 LIBXORP +741 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxorp/run_command.cc done ] Command /opt/vyatta/sbin/xorp_tmpl_tool: exited with exit status 1. Jan 27 14:20:41 localhost xorp_rtrmgr: [ 2008/01/27 15:20:41 ERROR xorp_rtrmgr:3758 RTRMGR +1647 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/task.cc execute_done ] Error found on program stderr! Jan 27 14:20:41 localhost xorp_rtrmgr: [ 2008/01/27 15:20:41 ERROR xorp_rtrmgr:3758 RTRMGR +701 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc commit_pass2_done ] Commit failed: VPN configuration error. The IKE group IKE-1W specified for peer 0.0.0.0 has not been configured. VPN configuration error. The ESP group ESP-1W specified for peer 0.0.0.0 tunnel 1 has not been configured. VPN configuration commit aborted due to error(s). Jan 27 14:22:41 localhost xorp_rtrmgr: [ 2008/01/27 15:22:41 ERROR xorp_rtrmgr:3758 LIBXORP +741 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxorp/run_command.cc done ] Command /opt/vyatta/sbin/xorp_tmpl_tool: exited with exit status 1. Jan 27 14:22:41 localhost xorp_rtrmgr: [ 2008/01/27 15:22:41 ERROR xorp_rtrmgr:3758 RTRMGR +1647 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/task.cc execute_done ] Error found on program stderr! Jan 27 14:22:41 localhost xorp_rtrmgr: [ 2008/01/27 15:22:41 ERROR xorp_rtrmgr:3758 RTRMGR +701 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc commit_pass2_done ] Commit failed: VPN configuration error. The IKE group IKE-1W specified for peer 0.0.0.0 has not been configured. VPN configuration error. The ESP group ESP-1W specified for peer 0.0.0.0 tunnel 1 has not been configured. VPN configuration commit aborted due to error(s). Jan 28 14:33:36 localhost pluto[4670]: ERROR: peer-yyy.xxx.zzz.qqq-tunnel-1 #1: sendto on eth0 to yyy.xxx.zzz.qqq:500 failed in main_outI1. Errno 101: Network is unreachable Jan 28 14:33:36 localhost ipsec__plutorun: 003 ERROR: peer-yyy.xxx.zzz.qqq-tunnel-1 #1: sendto on eth0 to yyy.xxx.zzz.qqq:500 failed in main_outI1. Errno 101: Network is unreachable Jan 28 14:33:40 localhost pluto[4670]: ERROR: peer-yyy.xxx.zzz.qqq-tunnel-1 #2: sendto on eth0 to yyy.xxx.zzz.qqq:500 failed in STATE_MAIN_R0. Errno 101: Network is unreachable Jan 28 14:33:46 localhost pluto[4670]: ERROR: peer-yyy.xxx.zzz.qqq-tunnel-1 #1: sendto on eth0 to yyy.xxx.zzz.qqq:500 failed in EVENT_RETRANSMIT. Errno 101: Network is unreachable Jan 28 14:33:50 localhost pluto[4670]: ERROR: peer-yyy.xxx.zzz.qqq-tunnel-1 #3: sendto on eth0 to yyy.xxx.zzz.qqq:500 failed in STATE_MAIN_R0. Errno 101: Network is unreachable ___ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
