An earnest appeal - please do fix APINGER in 2.2
-
GW of WAN and OPT1 are same, but monitoring IPs are different, and the connection of OPT1 is OK, i can ping any hosts from webgui with source address of opt1.
And bellow is a list of logs under System–>Gerneral:
Sep 24 19:59:51 syslogd: kernel boot file is /boot/kernel/kernel
Sep 24 19:59:51 kernel: Copyright (c) 1992-2014 The FreeBSD Project.
Sep 24 19:59:51 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Sep 24 19:59:51 kernel: The Regents of the University of California. All rights reserved.
Sep 24 19:59:51 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Sep 24 19:59:51 kernel: FreeBSD 10.1-PRERELEASE #32 30e366f(HEAD)-dirty: Wed Sep 24 05:03:13 CDT 2014
Sep 24 19:59:51 kernel: root@pf22-amd64-snap:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10 amd64
Sep 24 19:59:51 kernel: FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Sep 24 19:59:51 kernel: CPU: Intel(R) Pentium(R) CPU G3420 @ 3.20GHz (1803.48-MHz K8-class CPU)
Sep 24 19:59:51 kernel: Origin = "GenuineIntel" Id = 0x306c3 Family = 0x6 Model = 0x3c Stepping = 3
Sep 24 19:59:51 kernel: Features=0x1f83fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse,sse2,ss,htt>Sep 24 19:59:51 kernel: Features2=0xccd82203 <sse3,pclmulqdq,ssse3,cx16,sse4.1,sse4.2,movbe,popcnt,xsave,osxsave,rdrand,hv>Sep 24 19:59:51 kernel: AMD Features=0x20100800 <syscall,nx,lm>Sep 24 19:59:51 kernel: AMD Features2=0x21 <lahf,abm>Sep 24 19:59:51 kernel: Structured Extended Features=0x2200 <erms>Sep 24 19:59:51 kernel: real memory = 671088640 (640 MB)
Sep 24 19:59:51 kernel: avail memory = 608530432 (580 MB)
Sep 24 19:59:51 kernel: Event timer "LAPIC" quality 400
Sep 24 19:59:51 kernel: ACPI APIC Table: <vrtual microsft="">Sep 24 19:59:51 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Sep 24 19:59:51 kernel: FreeBSD/SMP: 1 package(s) x 2 core(s)
Sep 24 19:59:51 kernel: cpu0 (BSP): APIC ID: 0
Sep 24 19:59:51 kernel: cpu1 (AP): APIC ID: 1
Sep 24 19:59:51 kernel: ioapic0: Changing APIC ID to 0
Sep 24 19:59:51 kernel: ioapic0 <version 1.1="">irqs 0-23 on motherboard
Sep 24 19:59:51 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Sep 24 19:59:51 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff805f6300, 0) error 1
Sep 24 19:59:51 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Sep 24 19:59:51 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff805f63b0, 0) error 1
Sep 24 19:59:51 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Sep 24 19:59:51 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff805f6460, 0) error 1
Sep 24 19:59:51 kernel: iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Sep 24 19:59:51 kernel: iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff8061c640, 0) error 1
Sep 24 19:59:51 kernel: wlan: mac acl policy registered
Sep 24 19:59:51 kernel: iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Sep 24 19:59:51 kernel: iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff8061c6f0, 0) error 1
Sep 24 19:59:51 kernel: iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
Sep 24 19:59:51 kernel: iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
Sep 24 19:59:51 kernel: module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff8061c7a0, 0) error 1
Sep 24 19:59:51 kernel: random: <software, yarrow="">initialized
Sep 24 19:59:51 kernel: kbd1 at kbdmux0
Sep 24 19:59:51 kernel: vmbus0: <vmbus devices="">on motherboard
Sep 24 19:59:51 kernel: cryptosoft0: <software crypto="">on motherboard
Sep 24 19:59:51 kernel: padlock0: No ACE support.
Sep 24 19:59:51 kernel: acpi0: <vrtual microsft="">on motherboard
Sep 24 19:59:51 kernel: acpi0: Power Button (fixed)
Sep 24 19:59:51 kernel: acpi0: reservation of 0, a0000 (3) failed
Sep 24 19:59:51 kernel: acpi0: reservation of 100000, f7f00000 (3) failed
Sep 24 19:59:51 kernel: cpu0: <acpi cpu="">on acpi0
Sep 24 19:59:51 kernel: cpu1: <acpi cpu="">on acpi0
Sep 24 19:59:51 kernel: attimer0: <at timer="">port 0x40-0x43 irq 0 on acpi0
Sep 24 19:59:51 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Sep 24 19:59:51 kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Sep 24 19:59:51 kernel: atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
Sep 24 19:59:51 kernel: Event timer "RTC" frequency 32768 Hz quality 0
Sep 24 19:59:51 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Sep 24 19:59:51 kernel: acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
Sep 24 19:59:51 kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
Sep 24 19:59:51 kernel: pci0: <acpi pci="" bus="">on pcib0
Sep 24 19:59:51 kernel: isab0: <pci-isa bridge="">at device 7.0 on pci0
Sep 24 19:59:51 kernel: isa0: <isa bus="">on isab0
Sep 24 19:59:51 kernel: atapci0: <intel piix4="" udma33="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
Sep 24 19:59:51 kernel: ata0: <hyper-v ata="" storage="" disengage="" driver="">at channel 0 on atapci0
Sep 24 19:59:51 kernel: ata1: <ata channel="">at channel 1 on atapci0
Sep 24 19:59:51 kernel: pci0: <bridge>at device 7.3 (no driver attached)
Sep 24 19:59:51 kernel: vgapci0: <vga-compatible display="">mem 0xf8000000-0xfbffffff irq 11 at device 8.0 on pci0
Sep 24 19:59:51 kernel: vgapci0: Boot video device
Sep 24 19:59:51 kernel: atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
Sep 24 19:59:51 kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
Sep 24 19:59:51 kernel: kbd0 at atkbd0
Sep 24 19:59:51 kernel: atkbd0: [GIANT-LOCKED]
Sep 24 19:59:51 kernel: psm0: <ps 2="" mouse="">irq 12 on atkbdc0
Sep 24 19:59:51 kernel: psm0: [GIANT-LOCKED]
Sep 24 19:59:51 kernel: psm0: model IntelliMouse Explorer, device ID 4
Sep 24 19:59:51 kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Sep 24 19:59:51 kernel: uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Sep 24 19:59:51 kernel: fdc0: <floppy drive="" controller="" (fde)="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
Sep 24 19:59:51 kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0
Sep 24 19:59:51 kernel: orm0: <isa option="" rom="">at iomem 0xc0000-0xcbfff on isa0
Sep 24 19:59:51 kernel: sc0: <system console="">at flags 0x100 on isa0
Sep 24 19:59:51 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Sep 24 19:59:51 kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Sep 24 19:59:51 kernel: ppc0: cannot reserve I/O port range
Sep 24 19:59:51 kernel: Timecounter "Hyper-V" frequency 10000000 Hz quality 10000000
Sep 24 19:59:51 kernel: Timecounters tick every 10.000 msec
Sep 24 19:59:51 kernel: IPsec: Initialized Security Association Processing.
Sep 24 19:59:51 kernel: storvsc0 on vmbus0
Sep 24 19:59:51 kernel: storvsc1 on vmbus0
Sep 24 19:59:51 kernel: hyperv-utils0 on vmbus0
Sep 24 19:59:51 kernel: hyperv-utils0: Hyper-V Service attaching: Hyper-V Heartbeat Service
Sep 24 19:59:51 kernel:
Sep 24 19:59:51 kernel: hyperv-utils1 on vmbus0
Sep 24 19:59:51 kernel: hyperv-utils1: Hyper-V Service attaching: Hyper-V Shutdown Service
Sep 24 19:59:51 kernel:
Sep 24 19:59:51 kernel: hyperv-utils2 on vmbus0
Sep 24 19:59:51 kernel: hyperv-utils2: Hyper-V Service attaching: Hyper-V Time Synch Service
Sep 24 19:59:51 kernel:
Sep 24 19:59:51 kernel: hn0: <synthetic network="" interface="">on vmbus0
Sep 24 19:59:51 kernel: hn1: <synthetic network="" interface="">on vmbus0
Sep 24 19:59:51 kernel: hn2: <synthetic network="" interface="">on vmbus0
Sep 24 19:59:51 kernel: random: unblocking device.
Sep 24 19:59:51 kernel: cd0 at ata1 bus 0 scbus0 target 0 lun 0
Sep 24 19:59:51 kernel: cd0: <msft virtual="" cd="" rom="" 1.0="">Removable CD-ROM SCSI-5 device
Sep 24 19:59:51 kernel: cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes)
Sep 24 19:59:51 kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
Sep 24 19:59:51 kernel: da0 at blkvsc0 bus 0 scbus1 target 0 lun 0
Sep 24 19:59:51 kernel: da0: <msft virtual="" disk="" 1.0="">Fixed Direct Access SCSI-4 device
Sep 24 19:59:51 kernel: da0: 300.000MB/s transfers
Sep 24 19:59:51 kernel: da0: Command Queueing enabled
Sep 24 19:59:51 kernel: da0: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C)
Sep 24 19:59:51 kernel: SMP: AP CPU #1 Launched!
Sep 24 19:59:51 kernel: Trying to mount root from ufs:/dev/ufs/pfsense0 [ro,sync,noatime]…
Sep 24 19:59:51 kernel:
Sep 24 19:59:52 php: rc.bootup: Starting 3gstats.php on device '' for interface 'wan'
Sep 24 19:59:52 kernel:
Sep 24 19:59:52 php: rc.bootup: Starting 3gstats.php on device '' for interface 'opt1'
Sep 24 19:59:52 php: rc.bootup: Resyncing OpenVPN instances.
Sep 24 19:59:52 kernel: done.
Sep 24 19:59:52 kernel: pflog0: promiscuous mode enabled
Sep 24 19:59:52 php: rc.bootup: Could not find IPv4 gateway for interface (opt1).
Sep 24 19:59:52 php: rc.bootup: RRD create failed exited with 1, the error is: ERROR: creating '/var/db/rrd/WAN_PPPOE-quality.rrd': No such file or directory
Sep 24 19:59:52 kernel: ...done.
Sep 24 19:59:52 php: rc.bootup: The command '/usr/bin/nice -n20 /usr/local/bin/rrdtool update /var/db/rrd/WAN_PPPOE-quality.rrd N:U:U' returned exit code '1', the output was 'ERROR: opening '/var/db/rrd/WAN_PPPOE-quality.rrd': No such file or directory'
Sep 24 19:59:53 php-fpm[287]: /rc.newwanip: ROUTING: setting default route to 222.92.225.13
Sep 24 19:59:53 php-fpm[287]: /rc.newwanip: Removing static route for monitor 221.224.226.82 and adding a new route through 222.92.225.13
Sep 24 19:59:54 php-fpm[286]: /rc.newwanip: Removing static route for monitor 221.224.226.82 and adding a new route through 222.92.225.13
Sep 24 19:59:54 kernel: done.
Sep 24 19:59:55 kernel: done.
Sep 24 19:59:56 php: rc.bootup: ROUTING: setting default route to 222.92.225.13
Sep 24 19:59:56 kernel: done.
Sep 24 19:59:56 check_reload_status: Updating all dyndns
Sep 24 19:59:56 kernel: …..done.
Sep 24 20:00:00 php-fpm[286]: /rc.newwanip: phpDynDNS: updating cache file /conf/dyndns_opt1noip-free'pftest.ddns.net'2.cache: 221.225.73.206
Sep 24 20:00:00 php-fpm[286]: /rc.newwanip: phpDynDNS (pftest.ddns.net): (Success) DNS hostname update successful.
Sep 24 20:00:01 php: rc.bootup: Creating rrd update script
Sep 24 20:00:01 kernel: done.
Sep 24 20:00:01 php-fpm[286]: /rc.newwanip: Resyncing OpenVPN instances for interface OPT1.
Sep 24 20:00:01 kernel: done.
Sep 24 20:00:01 php-fpm[286]: /rc.newwanip: Creating rrd update script
Sep 24 20:00:02 php-fpm[287]: /rc.newwanip: phpDynDNS: updating cache file /conf/dyndns_wannoip-free'huiguang.no-ip.org'0.cache: 221.225.73.201
Sep 24 20:00:02 php-fpm[287]: /rc.newwanip: phpDynDNS (huiguang.no-ip.org): (Success) DNS hostname update successful.
Sep 24 20:00:02 php-fpm[285]: /rc.dyndns.update: phpDynDNS (huiguang.no-ip.org): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Sep 24 20:00:03 php-fpm[286]: /rc.newwanip: pfSense package system has detected an ip change 0.0.0.0 -> 221.225.73.206 … Restarting packages.
Sep 24 20:00:03 check_reload_status: Starting packages
Sep 24 20:00:03 check_reload_status: Reloading filter
Sep 24 20:00:03 php-fpm[286]: /rc.start_packages: Restarting/Starting all packages.
Sep 24 20:00:04 php-fpm[286]: /rc.start_packages: Restarting/Starting all packages.
Sep 24 20:00:04 php-fpm[287]: /rc.newwanip: phpDynDNS: updating cache file /conf/dyndns_wanhe-net'cloud.cutebox.net'1.cache: 221.225.73.201
Sep 24 20:00:05 login: login on ttyv0 as root
Sep 24 20:00:05 php-fpm[287]: /rc.newwanip: phpDynDNS: (Success) IP Address Updated Successfully!
Sep 24 20:00:05 php-fpm[285]: /rc.dyndns.update: phpDynDNS (cloud.cutebox.net): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Sep 24 20:00:05 sshlockout[83735]: sshlockout/webConfigurator v3.0 starting up
Sep 24 20:00:06 php-fpm[287]: /rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Sep 24 20:00:06 php-fpm[287]: /rc.newwanip: Creating rrd update script
Sep 24 20:00:06 php-fpm[285]: /rc.dyndns.update: phpDynDNS (pftest.ddns.net): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Sep 24 20:00:08 php-fpm[287]: /rc.newwanip: pfSense package system has detected an ip change 0.0.0.0 -> 221.225.73.201 … Restarting packages.
Sep 24 20:00:08 check_reload_status: Starting packages
Sep 24 20:00:08 check_reload_status: Reloading filter
Sep 24 20:00:09 php-fpm[285]: /rc.start_packages: Restarting/Starting all packages.
Sep 24 20:00:14 check_reload_status: updating dyndns OPT1_PPPOE
Sep 24 20:00:14 check_reload_status: Restarting ipsec tunnels
Sep 24 20:00:14 check_reload_status: Restarting OpenVPN tunnels/interfaces
Sep 24 20:00:14 check_reload_status: Reloading filter
Sep 24 20:00:15 php-fpm[285]: /rc.dyndns.update: phpDynDNS (pftest.ddns.net): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Sep 24 20:00:16 kernel: calcru: runtime went backwards from 522624 usec to 295023 usec for pid 285 (php-fpm)
…........(many lines same as above)
....................
Sep 24 20:01:08 kernel: calcru: runtime went backwards from 405510687 usec to 228805402 usec for pid 0 (kernel)
Sep 24 20:05:54 login: login on ttyv0 as root
Sep 24 20:06:20 php-fpm[285]: /index.php: Successful login for user 'admin' from: 58.214.197.206
Sep 24 20:06:20 php-fpm[285]: /index.php: Successful login for user 'admin' from: 58.214.197.206
Sep 24 20:09:10 login: login on ttyv0 as root
Sep 24 20:11:34 check_reload_status: Syncing firewallI could provide other info if needed.</msft></msft></synthetic></synthetic></synthetic></generic></system></isa></floppy></ps></at></keyboard></vga-compatible></bridge></ata></hyper-v></intel></isa></pci-isa></acpi></acpi></at></at></acpi></acpi></vrtual></software></vmbus></software,></version></vrtual></erms></lahf,abm></syscall,nx,lm></sse3,pclmulqdq,ssse3,cx16,sse4.1,sse4.2,movbe,popcnt,xsave,osxsave,rdrand,hv></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse,sse2,ss,htt>
-
I'm still not having much luck. I'm on Tuesdays beta build. I added two additional gateways for testing. I have my normal default gateway with monitor IP set to 8.8.8.8., another gateway with monitor IP set to my pfsense lan facing adapters IP, and the other gateway set to the default monitoring option (wan gateway IP, first hop outside my network)
All three show downs in the gateway log at the same time, multiple times. Latency is thru the roof on the gateway status area.
I will update to latest snap and turn on the additional logging and post my results. I'm almost wondering if something is crapping out with hyperv kernel modules, is anyone else having issues like this on their physical box?
See attached screens.
-
…and 45 minutes in on the Wednesday build I have "offline" for all gateways...even the fake one I setup that is the LAN adapter's IP address. I didn't get a chance to set one of the monitor IP's to an external IP, so there are two monitors that are my WAN default gateway and the other monitor is my LAN adapter IP address.
I had verbose logging on at the time. See attachments. I can provide other logs or info if needed.
-
I need the gateway logs if you have the new setting turned on.
Though from your description its not a good thing to do to setup a monitoring IP to your lan in general! -
I attached gateway logs to my last post. :)
Also, I was just adding a monitor to the lan IP just to see what it did, I am certain I'm not having a wan problem. It is odd that all gateways are being flagged down at the same time.
-
Multi-wan with static IPs and different gateways within each wan subnets are stable at least in my tests, but I use pppoe connections and we get the same gateway IP allmost all the times, so we have to set at least one monitor IP outside the wan subnet, and this line with outside monitor ip allways gets offline as the apinger reported, but the connection functional as normal.
If there is another to monitor the gatwway, that really helps.
I don't know if this is already known but I suspect this is where the issue exists for alot of people. I get the same problem and it only happens when the upstream gateways set by the ISP are the same. My ISP round-robin's two gateways when you establish a PPPOE connection. When I get differing gateways on connection it works right as rain.
When the same gateway is assigned to both connections the second WAN link will drop with the apinger issue. I can't even see how loadbalancing would be working in this situation either, as the routing table shows all connections just going out the default gateway. -
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
-
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
I'm in the same boat…static all around. Are you running pfSense virtualized or physical? If virtual, what hypervisor are you using? I'm curious if it's something related to Hyper-V or not. I want to move to ESX but haven't had a chance to do it quite yet.
I'm in a situation where I use it as a home router and host a monitoring server on the same box, so I have to do some type of virtualized solution.
-
In my case it's a pure static configuration. Static IP for the fw, static IP for the gateway, no load balancing.
I'm in the same boat…static all around. Are you running pfSense virtualized or physical?
My installation is physical, no virtualization.
-
My installation is physical, no virtualization.
Well so much for that idea…I was really hoping it was a hyper-v issue.
-
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
-
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
You must be new to a support role ;D
People are utterly fantastic at complaining about this, that and the other thing. The moment that they have to wiggle their little finger to help themselves, though, suddenly their problem is not quite so urgent or they just never quite get around to it. But they keep complaining…
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
This is a production unit. While I followed the 2.1 beta series, I haven't yet moved to 2.2 beta.
-
@KOM:
You must be new to a support role ;D
People are utterly fantastic at complaining about this, that and the other thing. The moment that they have to wiggle their little finger to help themselves, though, suddenly their problem is not quite so urgent or they just never quite get around to it. But they keep complaining…
Dude.
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
I attached my logs on reply 54, then when you asked for them in reply 55, I replied in reply 56 that they were attached to my previous post. You didn't respond asking for anything else, I do not know what else you want…
The gateway logs are on post 54. If you need other logs let me know and I will be glad to provide.
-
i need to see at least two logs since so many people complain about it.
That will give clues for the proper problem here. -
test
Why cant I copy/paste anything into this…
I write test and get no server error, but copy the log and I get unavailable/Nginx error.
-
The website cannot display the page
HTTP 500
Most likely causes:
•The website is under maintenance.
•The website has a programming error.What you can try:
Refresh the page.
Go back to the previous page.
More information More information
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.
-
Put it on gist.github.com and post the link?
-
https://gist.github.com/anonymous/7f15078fbe6c76e91502
