Raspberry Pi 2B VRS not starting

Bug reports and questions about running Virtual Radar Server on Linux
Post Reply
eddydude
Posts: 1
Joined: Tue Mar 01, 2016 11:46 am

Raspberry Pi 2B VRS not starting

Post by eddydude » Tue Mar 01, 2016 12:07 pm

I have installed mono and VRS and followed all the instructions given. I managed to open VRS once on my RaPi (ethernet to win10 + VNC). I wanted to configure VRS, but clicking on tools/options made VRS crash. Now it's impossible for me to even open VRS. I get the following log when inputting: 'mono VirtualRadar.exe'

pi@AeroboticaPi:~/Downloads $ mono VirtualRadar.exe
Xlib: extension "RANDR" missing on display ":1.0".
Missing method .ctor in assembly /usr/lib/mono/gac/Mono.Data.Sqlite/4.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll, type System.Security.SecurityRulesAttribute
Can't find custom attr constructor image: /usr/lib/mono/gac/Mono.Data.Sqlite/4.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll mtoken: 0x0a000222
* Assertion at class.c:5597, condition `!mono_loader_get_last_error ()' not met

Stacktrace:

at <unknown> <0xffffffff>
at VirtualRadar.Database.StandingData.StandingDataManager.CreateOpenConnection () <0x00047>
at VirtualRadar.Database.StandingData.StandingDataManager.GetDatabaseVersionNumber () <0x0003b>
at VirtualRadar.Database.StandingData.StandingDataManager.Load () <0x0003b>
at VirtualRadar.Library.Presenter.SplashPresenter.LoadStandingData () <0x000ab>
at VirtualRadar.Library.Presenter.SplashPresenter.StartApplication () <0x000e7>
at VirtualRadar.WinForms.SplashView.backgroundWorker_DoWork (object,System.ComponentModel.DoWorkEventArgs) <0x0004b>
at System.ComponentModel.BackgroundWorker.OnDoWork (System.ComponentModel.DoWorkEventArgs) <0x00037>
at System.ComponentModel.BackgroundWorker.ProcessWorker (object,System.ComponentModel.AsyncOperation,System.Threading.SendOrPostCallback) <0x0008f>
at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object_object_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:


Debug info from gdb:

[New LWP 1460]
[New LWP 1457]
[New LWP 1456]
[New LWP 1455]
[New LWP 1454]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
0x76e13c80 in poll () at ../sysdeps/unix/syscall-template.S:81
81 ../sysdeps/unix/syscall-template.S: No such file or directory.
Id Target Id Frame
6 Thread 0x75b7b430 (LWP 1454) "mono" 0x76e9aa40 in do_futex_wait (isem=isem@entry=0x3181a4) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
5 Thread 0x7331f430 (LWP 1455) "mono" 0x76e9c730 in nanosleep () at ../sysdeps/unix/syscall-template.S:81
4 Thread 0x732ff430 (LWP 1456) "mono" 0x76e9cee8 in __libc_waitpid (Cannot access memory at address 0x7e
pid=1458, stat_loc=0x732fce20, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40
3 Thread 0x72ee0430 (LWP 1457) "mono" 0x76e98b30 in __pthread_cond_timedwait (Cannot access memory at address 0x1
cond=0x1642b50, mutex=0x1642b34, abstime=0x72edf700) at pthread_cond_timedwait.c:199
2 Thread 0x72bff430 (LWP 1460) "mono" 0x76e9ac50 in do_futex_timed_wait (isem=isem@entry=0x317edc, rt=rt@entry=0x72bfecd8) at ../nptl/sysdeps/unix/sysv/linux/sem_timedwait.c:41
* 1 Thread 0x76fac000 (LWP 1453) "mono" 0x76e13c80 in poll () at ../sysdeps/unix/syscall-template.S:81

Thread 6 (Thread 0x75b7b430 (LWP 1454)):
#0 0x76e9aa40 in do_futex_wait (isem=isem@entry=0x3181a4) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
#1 0x76e9aaf4 in __new_sem_wait (sem=0x3181a4) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:69
#2 0x00219f98 in mono_sem_wait ()
#3 0x0019091c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0x7331f430 (LWP 1455)):
#0 0x76e9c730 in nanosleep () at ../sysdeps/unix/syscall-template.S:81
#1 0x0020e8b0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0x732ff430 (LWP 1456)):
Cannot access memory at address 0x7e
#0 0x76e9cee8 in __libc_waitpid (pid=1458, stat_loc=0x732fce20, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40
#1 0x000c0ba4 in ?? ()
Cannot access memory at address 0x7e
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x72ee0430 (LWP 1457)):
Cannot access memory at address 0x1
#0 0x76e98b30 in __pthread_cond_timedwait (cond=0x1642b50, mutex=0x1642b34, abstime=0x72edf700) at pthread_cond_timedwait.c:199
#1 0x001f68d8 in ?? ()
Cannot access memory at address 0x1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x72bff430 (LWP 1460)):
#0 0x76e9ac50 in do_futex_timed_wait (isem=isem@entry=0x317edc, rt=rt@entry=0x72bfecd8) at ../nptl/sysdeps/unix/sysv/linux/sem_timedwait.c:41
#1 0x76e9ad7c in sem_timedwait (sem=0x317edc, abstime=0x72bfed1c) at ../nptl/sysdeps/unix/sysv/linux/sem_timedwait.c:96
#2 0x0021a08c in mono_sem_timedwait ()
#3 0x001790f0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x76fac000 (LWP 1453)):
Cannot access memory at address 0x2
#0 0x76e13c80 in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x72f3eae4 in ?? ()
Cannot access memory at address 0x2
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted


Which gives me the impression that the problem actually lies with mono. Do you have any idea how to resolve this issue?

agw
Posts: 2241
Joined: Fri Feb 17, 2012 3:20 am

Re: Raspberry Pi 2B VRS not starting

Post by agw » Sat Mar 05, 2016 3:11 pm

When you say "+ VNC" do you mean you're using VNC to access the Pi? If so then it looks like you're not alone with getting RANDR error messages:

https://www.raspberrypi.org/forums/view ... 66&t=16598

Regarding the crash when you went into Tools | Options, this is a known issue with the WinForms implementation in the Pi's Mono. The web admin plugin (currently in preview) can be used to configure VRS on the Pi. You can get the latest preview version of the server and the web admin plugin from here:

http://www.virtualradarserver.co.uk/Preview.aspx

You'll need to set up an admin user in VRS, which you can do from the command-line (instructions here: http://forum.virtualradarserver.co.uk/v ... f=11&t=970). To avoid the Tools | Options crash, and perhaps avoid the X Windows crash you're getting in GUI mode, you can run the server in headless mode by adding the -noGui switch (mono ./VirtualRadar.exe -noGui).

Post Reply