nello
Patron
- Joined
- Dec 30, 2012
- Messages
- 351
I get these error messages every hour:
Can anyone give me an idea how to fix this problem?
Thank you.
- nello
UPDATE 2016.01.28
I'm still getting these errors even after a reboot:
I'm able to download the .pem file just fine through a browser on another computer on the LAN:
I corrected an error in the subnet mask for my FreeNAS network interface and since rebooting the error hasn't appeared. So I guess the problem was an error in the way I'd configured the interface.
Code:
Jan 28 03:52:59 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 03:52:59 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 03:54:15 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 03:54:15 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 04:56:12 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 04:56:12 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 04:57:28 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 04:57:28 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 05:59:24 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 05:59:24 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 06:00:40 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 06:00:40 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 07:02:37 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 07:02:37 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 07:03:53 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 07:03:53 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 08:05:47 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 08:05:47 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 08:07:03 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 08:07:03 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem
Can anyone give me an idea how to fix this problem?
Thank you.
- nello
UPDATE 2016.01.28
I'm still getting these errors even after a reboot:
Code:
Jan 28 10:05:30 OctoberGroupNAS kernel: epair3a: link state changed to UP Jan 28 10:05:30 OctoberGroupNAS kernel: epair3a: link state changed to UP Jan 28 10:05:30 OctoberGroupNAS kernel: epair3b: link state changed to UP Jan 28 10:05:30 OctoberGroupNAS kernel: epair3b: link state changed to UP Jan 28 10:05:30 OctoberGroupNAS kernel: epair3a: promiscuous mode enabled Jan 28 10:05:30 OctoberGroupNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b Jan 28 10:05:30 OctoberGroupNAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b Jan 28 10:06:05 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 10:06:06 OctoberGroupNAS syslog-ng[10049]: syslog-ng starting up; version='3.5.6' Jan 28 10:06:06 OctoberGroupNAS kernel: pid 1854 (syslog-ng), uid 0: exited on signal 6 (core dumped) Jan 28 10:06:45 OctoberGroupNAS autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "red@auto-20160128.1006-1m" Jan 28 10:06:45 OctoberGroupNAS autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "red@auto-20151229.1000-1m" Jan 28 10:07:21 OctoberGroupNAS alert.py: [freenasOS.Configuration:597] Unable to load https://web.ixsystems.com/updates/ix_crl.pem: <urlopen error [Errno 60] Operation timed out> Jan 28 10:07:21 OctoberGroupNAS alert.py: [freenasOS.Manifest:386] Could not get CRL file https://web.ixsystems.com/updates/ix_crl.pem Jan 28 10:07:40 OctoberGroupNAS kernel: arp: 10.10.49.10 moved from 02:25:98:00:0e:0a to 68:05:ca:3e:ac:f2 on epair0b
I'm able to download the .pem file just fine through a browser on another computer on the LAN:
Code:
-----BEGIN X509 CRL----- MIICzjCBtzANBgkqhkiG9w0BAQsFADByMQswCQYDVQQGEwJVUzELMAkGA1UECAwC Q0ExETAPBgNVBAcMCFNhbiBKb3NlMRowGAYDVQQDDBF3d3cuaXhzeXN0ZW1zLmNv bTEnMCUGCSqGSIb3DQEJARYYaG9zdG1hc3RlckBpeHN5c3RlbXMuY29tFw0xNDEx MTkxODMyNDFaFw0xNDEyMTkxODMyNDFaMBQwEgIBARcNMTQxMDIyMTgwOTIwWjAN BgkqhkiG9w0BAQsFAAOCAgEAPrnWIWhlksDu2JrVozc7/dWfuaqUHc3nawURA0yi NkF++llmjA7pXrMtNudgN+LhjyKYFPQQTk10UFV8DgRiMVCiC0CujcoSxRQXCEIh wITCWBg/WsILUPjYZZLivwxKYkUstW0oPgLIf3Wu4fE/iT1jlHgMNJEhjRAEQYuj p4MDVgizhSOBtZeHHHdJnwv9Esq9fHIJf+Ic9GtJh166bXokkIPf0a2b2HSMr2+H nGib6QHzdkfTZZ0LeL5S7OwYDQ4StyyT3RKUbUa3xWLaC3gJMJ9kD2ZMufMX35tX fJ1z3bQ0SC97g3JuqQfB5n00kiUC/vZdGqqsIJPxBNdZ8rHLPQ8f4MYkvFV2a3iE 0QqIRxlLZSXJKqw+Mu5IyiTapam1nrHrjpvxqQQn8gMCbCpeLySMMJ2B2ybU1Z9C DZR+j80ukTBJlQ7Btli2K56cE1/c1ToO6BIdCEOL6Ye/eE8x3yOWTkXSIU8fC1Ge TEtOydomOv/bkMT+jw+S9vwPj74ELk7S7CoiVMNjGvHVKxu//40BM1DMyl4Xzsr5 N/2xkVTF0Vf0SM3D9OTk/KwhAF7FSh+ogsnBEoPPmYLb0iVVX2GN+C2cn9/eSXX7 Woo1cknSkiNswnQwbWJlgiGikWMDBONYmva1AG8qqVGGP54li2iO7vQm6i1KMjFJ z8c= -----END X509 CRL-----
I corrected an error in the subnet mask for my FreeNAS network interface and since rebooting the error hasn't appeared. So I guess the problem was an error in the way I'd configured the interface.
Last edited: