Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 1517 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade 9.100-16 -> RED lost

dapor
Hello,

after I updatet my UTM to Firmware 9.100-16, the AP and RED had to make also a firmwarepatch.

The APs had had hard to work for it and after 10 to 15 minutes they are online again again.

But my RED Device isnt rechable since the firmware patch and the last log entry is: 


2013:05:16-14:29:09 dapor red_server[4230]: id="4201" severity="info" sys="System" sub="RED" name="RED Tunnel Up" red_id="A320033511C16B3" forced="0"

2013:05:16-14:29:12 dapor red_server[4230]: A320033511C16B3: command 'FWUPDATE device=RED10R2 version=2016R2'

2013:05:16-14:29:12 dapor red_server[4230]: A320033511C16B3: Sending /usr/share/red-firmware/userland-v2016R2 to device

2013:05:16-14:29:13 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:30:21 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:30:22 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:30:34 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:31:28 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:31:34 dapor red_server[4609]: SELF: (Re-)loading device configurations

2013:05:16-14:32:12 dapor red_server[4230]: >=========================================================================

2013:05:16-14:32:12 dapor red_server[4230]: DIE --------------------------------------------------------

2013:05:16-14:32:12 dapor red_server[4230]: 

2013:05:16-14:32:12 dapor red_server[4230]:  1. main::__ANON__:48() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  2. main::__ANON__:762() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  3. (eval):558() blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/ssl_write_all.al)

2013:05:16-14:32:12 dapor red_server[4230]:  4. Net::SSLeay::ssl_write_all:558() blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/ssl_write_all.al)

2013:05:16-14:32:12 dapor red_server[4230]:  5. IO::Socket::SSL::generic_write:782() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  6. IO::Socket::SSL::write:803() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  7. IO::Socket::SSL:[[[:P]]]rint:816() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  8. IO::Socket::SSL::SSL_HANDLE:[[:P]]RINT:1490() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  9. (eval):771() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  10. main::transfer_fw:761() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  11. main::handle_fw_update_cmd:827() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  12. main::run_client_red10:1005() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  13. main::run_client:455() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  14. main::socketListener:337() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  15. main::top-level:278() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]: |=========================================================================

2013:05:16-14:32:12 dapor red_server[4230]: Firmware update timed out at red_server.pl line 762.

2013:05:16-14:32:12 dapor red_server[4230]: 

2013:05:16-14:32:12 dapor red_server[4230]:  1. main::__ANON__:49() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  2. main::__ANON__:762() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  3. (eval):558() blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/ssl_write_all.al)

2013:05:16-14:32:12 dapor red_server[4230]:  4. Net::SSLeay::ssl_write_all:558() blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/ssl_write_all.al)

2013:05:16-14:32:12 dapor red_server[4230]:  5. IO::Socket::SSL::generic_write:782() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  6. IO::Socket::SSL::write:803() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  7. IO::Socket::SSL:[[[:P]]]rint:816() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  8. IO::Socket::SSL::SSL_HANDLE:[[:P]]RINT:1490() /usr/local/ap510/site/lib/IO/Socket/SSL.pm

2013:05:16-14:32:12 dapor red_server[4230]:  9. (eval):771() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  10. main::transfer_fw:761() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  11. main::handle_fw_update_cmd:827() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  12. main::run_client_red10:1005() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  13. main::run_client:455() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  14. main::socketListener:337() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]:  15. main::top-level:278() red_server.pl

2013:05:16-14:32:12 dapor red_server[4230]: 


this is repeating about 2 times a hour.....


This thread was automatically locked due to age.
Parents
  • 0
    What happens if the RED is hard rebooted (power off/on)?

    If that doesn't work, you should get a support ticket opened.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    What happens if the RED is hard rebooted (power off/on)?

    If that doesn't work, you should get a support ticket opened.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    What happens if the RED is hard rebooted (power off/on)?

    If that doesn't work, you should get a support ticket opened.

    Cheers - Bob


    I will test this at the weekend, because the RED is locatted in an human free office [;)]

    Is it possible that the Firmwarepatch is too big for the small wan connection ??

    is it possible to to Flash the RED manual ??

    Thx
Cookie Information Banner