FGTracker
Recent news

[05/29/2024] Moved to new se...

[08/12/2023] fgtracker.ml �...

FAQ Categories

« 1 2 3 (4) 5 6 7 8 »
Posted by hazuki On 2014/10/3 15:47:48 (1475 reads)

Since the transfer of sovereignty over Hong Kong, the Chinese government is taking more and more control over Hong Kong in a way that the Sino-British joint declaration is de facto being violated.  In a foreseeable future (may be quit near due to political instability of Hong Kong), communications in Hong Kong will be monitored and controlled.  This likely lead to service termination of FGTracker.  In this regard, I am seeking to move the FGTracker out of Hong Kong.  Since FGTracker is currently running on my interest and no money donation is received, your help is really appreciated.

What I need is an IaaS environment with the following features:

 

  1. Debian/Redhat based
  2. Unlimited traffic (static IP is preferred)
  3. SSH shell, SFTP, apache, postgresql, mysql, PHP with certain extensions
  4. Gcc with certain file headers for compiling FGTracker
  5. 2GB Ram
  6. 120GB+2GB space (120GB must be in SSD for running postgresql database + 2GB webpage hosting)

I know the above environment is costly but this is exactly the same environment (and the minimum requirement for) the FGTracking running.  If you have such environment available, please do not hesitate to contact me at hatsuki_a-ie AT  yahoo.com.hk.  Thank you!

Posted by hazuki On 2014/5/30 13:49:27 (861 reads)

There will be interruption of service sometime between 31.05.2014 0200 UTC and 02.06.2014 1500 UTC as I will arrange router upgrade (for anyone interest: from Buffalo to EdgeRouter) for fgtracker. The interruption should be occured few times for a short time within the above-mentioned period.

Posted by hazuki On 2014/4/17 2:31:59 (658 reads)

... By replacing the motherboard and CPU...

Posted by hazuki On 2014/4/5 2:04:22 (817 reads)

Hi all,

Recentely mpserver15 is facing some hardware/driver problem which leads the server offline, and the only way to bring the server back is to restart it. I have tried to use some older kernels but the issue still presists.

Mpserver15 runs in Ubuntu 10.04 LTS and I really hope anybody can direct me to the solution. Below is the log related to the issue:

 

Apr  4 21:06:27 AC-SERVER kernel: [478876.033775] i2c i2c-3: sendbytes: NAK bailout.
Apr  4 21:36:31 AC-SERVER kernel: [480680.258273] i2c i2c-3: sendbytes: NAK bailout.
Apr  4 22:49:51 AC-SERVER kernel: [485080.001554] i2c i2c-3: sendbytes: NAK bailout.
Apr  5 01:45:01 AC-SERVER kernel: [495589.824021] ------------[ cut here ]------------
Apr  5 01:45:01 AC-SERVER kernel: [495589.824034] WARNING: at /build/buildd/linux-3.2.0/net/sched/sch_generic.c:255 dev_watchdog+0x25a/0x270()
Apr  5 01:45:01 AC-SERVER kernel: [495589.824037] Hardware name: Unknow
Apr  5 01:45:01 AC-SERVER kernel: [495589.824039] NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
Apr  5 01:45:01 AC-SERVER kernel: [495589.824041] Modules linked in: usblp tcp_diag inet_diag btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext2 dm_crypt snd_hda_codec_hdmi rfcomm bnep parport_pc bluetooth ppdev binfmt_misc snd_hda_codec_realtek ip6t_LOG snd_hda_intel xt_hl snd_hda_codec snd_hwdep ip6t_rt snd_pcm nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT ipt_LOG snd_seq_midi xt_limit snd_rawmidi snd_seq_midi_event xt_tcpudp snd_seq xt_addrtype snd_timer snd_seq_device xt_state ip6table_filter snd ip6_tables soundcore nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack iptable_filter serio_raw sp5100_tco i2c_piix4 shpchp snd_page_alloc k8temp hwmon_vid ip_tables edac_core edac_mce_amd x_tables mac_hid lp parport pata_atiixp radeon floppy ttm drm_kms_helper drm i2c_algo_bit r8169
Apr  5 01:45:01 AC-SERVER kernel: [495589.824107] Pid: 9049, comm: gzip Not tainted 3.2.0-57-generic #87-Ubuntu
Apr  5 01:45:01 AC-SERVER kernel: [495589.824109] Call Trace:
Apr  5 01:45:01 AC-SERVER kernel: [495589.824112]  <IRQ>  [<ffffffff810681af>] warn_slowpath_common+0x7f/0xc0
Apr  5 01:45:01 AC-SERVER kernel: [495589.824122]  [<ffffffff810682a6>] warn_slowpath_fmt+0x46/0x50
Apr  5 01:45:01 AC-SERVER kernel: [495589.824126]  [<ffffffff810251b2>] ? x86_pmu_enable+0x1f2/0x270
Apr  5 01:45:01 AC-SERVER kernel: [495589.824133]  [<ffffffff8156598a>] dev_watchdog+0x25a/0x270
Apr  5 01:45:01 AC-SERVER kernel: [495589.824137]  [<ffffffff81112750>] ? perf_rotate_context+0x110/0x220
Apr  5 01:45:01 AC-SERVER kernel: [495589.824141]  [<ffffffff81565730>] ? qdisc_reset+0x50/0x50
Apr  5 01:45:01 AC-SERVER kernel: [495589.824144]  [<ffffffff81565730>] ? qdisc_reset+0x50/0x50
Apr  5 01:45:01 AC-SERVER kernel: [495589.824149]  [<ffffffff8107716b>] call_timer_fn+0x3b/0x150
Apr  5 01:45:01 AC-SERVER kernel: [495589.824154]  [<ffffffff8131529d>] ? rb_insert_color+0xad/0x150
Apr  5 01:45:01 AC-SERVER kernel: [495589.824157]  [<ffffffff81565730>] ? qdisc_reset+0x50/0x50
Apr  5 01:45:01 AC-SERVER kernel: [495589.824161]  [<ffffffff81078ab2>] run_timer_softirq+0x132/0x2a0
Apr  5 01:45:01 AC-SERVER kernel: [495589.824165]  [<ffffffff81096365>] ? ktime_get+0x65/0xe0
Apr  5 01:45:01 AC-SERVER kernel: [495589.824169]  [<ffffffff8106fa08>] __do_softirq+0xa8/0x210
Apr  5 01:45:01 AC-SERVER kernel: [495589.824173]  [<ffffffff8109d324>] ? tick_program_event+0x24/0x30
Apr  5 01:45:01 AC-SERVER kernel: [495589.824178]  [<ffffffff8166bdec>] call_softirq+0x1c/0x30
Apr  5 01:45:01 AC-SERVER kernel: [495589.824183]  [<ffffffff810162f5>] do_softirq+0x65/0xa0
Apr  5 01:45:01 AC-SERVER kernel: [495589.824186]  [<ffffffff8106fdee>] irq_exit+0x8e/0xb0
Apr  5 01:45:01 AC-SERVER kernel: [495589.824189]  [<ffffffff8166c79e>] smp_apic_timer_interrupt+0x6e/0x99
Apr  5 01:45:01 AC-SERVER kernel: [495589.824193]  [<ffffffff8166a65e>] apic_timer_interrupt+0x6e/0x80
Apr  5 01:45:01 AC-SERVER kernel: [495589.824195]  <EOI>  [<ffffffff81669b82>] ? system_call_fastpath+0x16/0x1b
Apr  5 01:45:01 AC-SERVER kernel: [495589.824201] ---[ end trace 067845823985b4b6 ]---
Apr  5 01:45:01 AC-SERVER kernel: [495589.850247] r8169 0000:02:00.0: eth1: link up
Apr  5 01:45:13 AC-SERVER kernel: [495601.850256] r8169 0000:02:00.0: eth1: link up
Apr  5 01:45:37 AC-SERVER kernel: [495625.850300] r8169 0000:02:00.0: eth1: link up
Apr  5 01:46:37 AC-SERVER kernel: [495685.850239] r8169 0000:02:00.0: eth1: link up
Apr  5 01:47:25 AC-SERVER kernel: [495733.850243] r8169 0000:02:00.0: eth1: link up
Apr  5 01:48:01 AC-SERVER kernel: [495769.850281] r8169 0000:02:00.0: eth1: link up

 

And network card detail is as follows:

i@AC-SERVER:/var/log$ lspci | awk '/net/ {print $1}' | xargs -i% lspci -ks %
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
        Kernel driver in use: r8169
        Kernel modules: r8169

 

Any help is appreciated. To contact me, please email to hatsuki_a-ie   屌at屌 yahoo.com.hk

Posted by hazuki On 2014/3/22 14:31:51 (760 reads)

Due to low usage and high operation cost on maintaining mpserver15, this site (mpserver15.flightgear.org) will cease act as mpserver with effect from 01.04.2014. Other service (i.e. FGTracker) will remain unchange.