×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDIHUB.SPACE

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

What happened here?

stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos-INDIHUB -indi-server-manager=localhost:8624 -mode=share
2021/09/30 12:19:52 Connection to local INDI-Server Manager on localhost:8624...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:52 INDI-server is running with active INDI-profile 'NMCosmos-INDIHUB'
2021/09/30 12:19:52 INDIDrivers:
2021/09/30 12:19:52 {Binary:indi_astrometry Skeleton:<nil> Family:Auxiliary Label:Astrometry Version:0.1 Role: Custom:false Name:Astrometry}
2021/09/30 12:19:52 {Binary:indi_sx_ccd Skeleton:<nil> Family:CCDs Label:SX CCD Version:1.15 Role: Custom:false Name:SX CCD}
2021/09/30 12:19:52 {Binary:indi_asi_ccd Skeleton:<nil> Family:CCDs Label:ZWO CCD Version:2.0 Role: Custom:false Name:ZWO CCD}
2021/09/30 12:19:52 {Binary:indi_nexdome Skeleton:<nil> Family:Domes Label:NexDome Version:1.6 Role: Custom:false Name:NexDome}
2021/09/30 12:19:52 {Binary:indi_asi_wheel Skeleton:<nil> Family:Filter Wheels Label:ASI EFW Version:2.0 Role: Custom:false Name:ASI EFW}
2021/09/30 12:19:52 {Binary:indi_sestosenso2_focus Skeleton:<nil> Family:Focusers Label:Esatto Version:0.7 Role: Custom:false Name:Sesto Senso 2}
2021/09/30 12:19:52 {Binary:indi_ioptronv3_telescope Skeleton:<nil> Family:Telescopes Label:iOptron CEM120 Version:1.4 Role: Custom:false Name:iOptronV3}
2021/09/30 12:19:52 {Binary:indi_aagcloudwatcher_ng Skeleton:<nil> Family:Weather Label:AAG Cloud Watcher NG Version:1.6 Role: Custom:false Name:AAG Cloud Watcher NG}
2021/09/30 12:19:52 Test connection to local INDI-Server on localhost:7624...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:52 Connecting to the indihub.space cloud...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:53 Current agent version: 1.0.6
2021/09/30 12:19:53 Access token: 048b2866ac37496880490a4a21f520ca
2021/09/30 12:19:53 Host session token: 6600444a9113473aaa7b006f108e804f
2021/09/30 12:19:53 Starting INDI-Server in the cloud...
2021/09/30 12:19:53 ...OK

                                ************************************************************
                                *               INDIHUB public address list!!              *
                                ************************************************************
                                                                                            
                                   INDI-Server: node-1.indihub.io:53023
                                                                                            
                                ************************************************************

                                Please provide your guest with this information:

                                1. Public address list from the above
                                2. Focal length and aperture of your main telescope
                                3. Focal length and aperture of your guiding telescope
                                4. Type of guiding you use: PHD2 or guiding via camera
                                5. Names of your imaging camera and guiding cameras

                                NOTE: These public addresses will be available ONLY until
                                agent is running! (Ctrl+C will stop the session)

2021/09/30 12:19:53 API-server error: listen tcp :2020: bind: address already in use
stellarmate@stellarmate:~ $ 
 
Last edit: 2 years 5 months ago by Peter Kennett.
2 years 5 months ago #76166

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Looks like the issue was solved!
The "share" mode is mostly to invite guests to use your equipment but you could use it remotely yourself if equipment is automated enough (dome and etc.)
2 years 5 months ago #76186

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Yeah my main goal is to be able to operate my Stellarmate in my observatory while traveling. Anyway, I am close, but still not able to connect.
I keep getting the error I posted above "2021/09/30 12:19:53 API-server error: listen tcp :2020: bind: address already in use"
2 years 5 months ago #76187

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Looks like the share-session started successfully (it showed "node-1.indihub.io:53023" public endpoint which can be used by guest in KStars/Ekos).

According to "API-server error: listen tcp :2020: bind: address already in use" error
- looks like agent was already running in a background or in other terminal? indihub-agent starts server on a port 2020 and that port was already taken.
Try command "ps -ef | grep indihub-agent" to see if it is already running (i.e. it could be launched from INDI Web Manager).

If you are sure that no other copy if indihub-agent is running that would mean some other program on stellarmate takes that port. Not a big deal though, you can use "-api-port=N" parameter where N is some other free port, i.e. 8787 or something.
2 years 5 months ago #76188

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Ok, using a different port worked, but when I tried to connect with a different computer I got :

2021-09-30T19:31:46 Failed to connect to remote INDI server.
2021-09-30T19:31:46 Connecting to remote INDI server at INDI-Server: node-1.indihub.io:53362 on port 8,787 …

For some reason it can't see the URL for the remote INDI server.

The remote INDI server shows:

 


I think I need full BASIC instructions to include what to do on the remote version of KStars (on my Stellarmate) and then what to do on the local PC. I followed the screen shots, but I am not able to connect. The INDI server is running though.  Must be some simple step I am missing.
2 years 5 months ago #76189
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Aha, looking at you terminal screenshot I see that share-session was started successfully.

Now, on your remote PC you would need to launch KStars/Ekos and create profile for your remote-connection - please see attachment with arrows where you need to enter information. Then save this profile and try to connect. You should see all your equipment in Ekos controlled remotely.

That api-port=8787 is internal thing not needed by guest, sorry it is confusing (that port actually used to communicate with indihub-agent from INDI Web Manager if you decide to use it). All guest would need to know is INDI-server public host node-1.indihub.io and port 53362. Please note - this public host and port is alive as long as indihub-agent is running that session, if you stop and start indihub-agent in share-mode again then it will be other host and port.

Hope that helps!

According to guiding - I would try 1st KStars/Ekos internal guiding to have remote access working.
I've noticed on your screenshot PHD2 icon, indihub-agent actually can provide to PHD2 remote access as well, so guest can create remote profile in KStars/Ekos with PHD2 guiding.
 
Last edit: 2 years 5 months ago by Denis.
2 years 5 months ago #76190
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

According to stellarmate - all you need to run stellarmate are indihub-agent connected to indiserver. (you don't need to run KStars on stellarmate).
On the local PC - you run KStars and create Ekos profile for remote connection (from my previous message).

So the connection schema looks like this:
KStars(local PC) <---> Intentet <---> indihub-agent(stellarmate) <---> indi-server (stelatmate) <---> equipment
2 years 5 months ago #76192

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

I tried dozens of times to get PHD2 to control my CEM120 EC2 mount, and could never get consistent results. Most if the time it was unusable as it fought with my encoders, a few nights I got it working, but then it failed later in the night. It’s the DEC encoder that goes nuts with PHD2. EKOS works better.
2 years 5 months ago #76194

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Thanks again for your continued help Denis. I tried to run INDIHUB without launching in to KStars and got this result:

stellarmate@stellarmate:~ $
stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos-INDIHUB -indi-server-manager=localhost:8624 -mode=share -api-port=8787
2021/10/01 08:38:58 Connection to local INDI-Server Manager on localhost:8624...
2021/10/01 08:38:58 ...OK
2021/10/01 08:38:58 Setting active INDI-profile to 'NMCosmos-INDIHUB'
stellarmate@stellarmate:~ $

It did not start up INDIHUB. What am I missing?
2 years 5 months ago #76213

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

SUCCESS!!!

I didn't realize that I had to separate this line from the INDIHUB server:

INDI-Server: node-1.indihub.io:55518 and separate the host URL and PORT.

Once I took "node-1.indihub.io" and "55518" and place them into HOST and PORT sections, it started right up. I was pasting the whole line "INDI-SERVER: node-1.indihub.io:55518" into the Host block.

 
The following user(s) said Thank You: Jasem Mutlaq
2 years 5 months ago #76214

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

While INDIHUB started up - it soon crashed my Mac to the desktop.





Process:               kstars [21830]
Path:                  /Applications/Astronomy/KStars.app/Contents/MacOS/kstars
Identifier:            ???
Version:               3.5.4 (3.5.4)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           kstars [21830]
User ID:               501

Date/Time:             2021-10-01 08:53:22.079 -0600
OS Version:            Mac OS X 10.15.7 (19H1217)
Report Version:        12
Anonymous UUID:        27E6B7BF-B4F3-F03B-E0EA-E3AE3C5F421F

Sleep/Wake UUID:       FC015808-125B-4C87-8561-3CE358B16B35

Time Awake Since Boot: 670000 seconds
Time Since Wake:       3200 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       EXC_I386_GPFLT
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [21830]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib          0x00007fff67dd8e52 _platform_strlen + 18
1                                     0x000000010e2bb873 0x10e2a1000 + 108659
2                                     0x000000010e3786b5 0x10e2a1000 + 882357
3                                     0x000000010e37a952 0x10e2a1000 + 891218
4   org.qt-project.QtCore             0x00000001121835a4 QObject::event(QEvent*) + 900
5   org.qt-project.QtWidgets          0x0000000111215746 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
6   org.qt-project.QtWidgets          0x0000000111216afd QApplication::notify(QObject*, QEvent*) + 477
7   org.qt-project.QtCore             0x000000011215aa16 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 166
8   org.qt-project.QtCore             0x000000011215bb53 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 803
9   libqcocoa.dylib                   0x0000000114faa042 0x114f6f000 + 241730
10  libqcocoa.dylib                   0x0000000114faa768 0x114f6f000 + 243560
11  com.apple.CoreFoundation          0x00007fff2db257e2 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12  com.apple.CoreFoundation          0x00007fff2db25781 __CFRunLoopDoSource0 + 103
13  com.apple.CoreFoundation          0x00007fff2db2559b __CFRunLoopDoSources0 + 209
14  com.apple.CoreFoundation          0x00007fff2db242ca __CFRunLoopRun + 927
15  com.apple.CoreFoundation          0x00007fff2db238ce CFRunLoopRunSpecific + 462
16  com.apple.HIToolbox               0x00007fff2c74fabd RunCurrentEventLoopInMode + 292
17  com.apple.HIToolbox               0x00007fff2c74f7d5 ReceiveNextEventCommon + 584
18  com.apple.HIToolbox               0x00007fff2c74f579 _BlockUntilNextEventMatchingListInModeWithFilter + 64
19  com.apple.AppKit                  0x00007fff2ad96039 _DPSNextEvent + 883
20  com.apple.AppKit                  0x00007fff2ad94880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
21  com.apple.AppKit                  0x00007fff2ad8658e -[NSApplication run] + 658
22  libqcocoa.dylib                   0x0000000114fa9414 0x114f6f000 + 238612
23  org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
24  org.qt-project.QtCore             0x000000011215afb2 QCoreApplication::exec() + 130
25                                    0x000000010e2b8c02 0x10e2a1000 + 97282
26  libdyld.dylib                     0x00007fff67be2cc9 start + 1

Thread 1:
0   libsystem_pthread.dylib           0x00007fff67de2b68 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib           0x00007fff67de2b68 start_wqthread + 0

Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib            0x00007fff67d2c0fe __select + 10
1   com.apple.CoreFoundation          0x00007fff2db4e6f3 __CFSocketManager + 641
2   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
3   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 4:: QDBusConnectionManager
0   libsystem_kernel.dylib            0x00007fff67d2a3d6 poll + 10
1   org.qt-project.QtCore             0x00000001121b7eee qt_safe_poll(pollfd*, unsigned int, timespec const*) + 94
2   org.qt-project.QtCore             0x00000001121b971a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 810
3   org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
4   org.qt-project.QtCore             0x0000000111f9a063 QThread::exec() + 131
5   org.qt-project.QtDBus             0x00000001108d9163 0x1108d5000 + 16739
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 5:: Thread (pooled)
0   libsystem_kernel.dylib            0x00007fff67d26882 __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff67de7425 _pthread_cond_wait + 698
2   org.qt-project.QtCore             0x0000000111fa2f50 0x111f79000 + 171856
3   org.qt-project.QtCore             0x0000000111fa2c7e 0x111f79000 + 171134
4   org.qt-project.QtCore             0x0000000111fa2bd3 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83
5   org.qt-project.QtCore             0x0000000111f9f4b5 0x111f79000 + 156853
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 6:: Thread (pooled)
0   libsystem_kernel.dylib            0x00007fff67d26882 __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff67de7425 _pthread_cond_wait + 698
2   org.qt-project.QtCore             0x0000000111fa2f50 0x111f79000 + 171856
3   org.qt-project.QtCore             0x0000000111fa2c7e 0x111f79000 + 171134
4   org.qt-project.QtCore             0x0000000111fa2bd3 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83
5   org.qt-project.QtCore             0x0000000111f9f4b5 0x111f79000 + 156853
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 7:: Thread (pooled)
0   libsystem_kernel.dylib            0x00007fff67d26882 __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff67de7425 _pthread_cond_wait + 698
2   org.qt-project.QtCore             0x0000000111fa2f50 0x111f79000 + 171856
3   org.qt-project.QtCore             0x0000000111fa2c7e 0x111f79000 + 171134
4   org.qt-project.QtCore             0x0000000111fa2bd3 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83
5   org.qt-project.QtCore             0x0000000111f9f4b5 0x111f79000 + 156853
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 8:: Thread (pooled)
0   libsystem_kernel.dylib            0x00007fff67d26882 __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff67de7425 _pthread_cond_wait + 698
2   org.qt-project.QtCore             0x0000000111fa2f50 0x111f79000 + 171856
3   org.qt-project.QtCore             0x0000000111fa2c7e 0x111f79000 + 171134
4   org.qt-project.QtCore             0x0000000111fa2bd3 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83
5   org.qt-project.QtCore             0x0000000111f9f4b5 0x111f79000 + 156853
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 9:: com.apple.NSEventThread
0   libsystem_kernel.dylib            0x00007fff67d23dfa mach_msg_trap + 10
1   libsystem_kernel.dylib            0x00007fff67d24170 mach_msg + 60
2   com.apple.CoreFoundation          0x00007fff2db25985 __CFRunLoopServiceMachPort + 247
3   com.apple.CoreFoundation          0x00007fff2db24452 __CFRunLoopRun + 1319
4   com.apple.CoreFoundation          0x00007fff2db238ce CFRunLoopRunSpecific + 462
5   com.apple.AppKit                  0x00007fff2af37954 _NSEventThread + 132
6   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
7   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 10:: Qt bearer thread
0   libsystem_kernel.dylib            0x00007fff67d2a3d6 poll + 10
1   org.qt-project.QtCore             0x00000001121b7f6c qt_safe_poll(pollfd*, unsigned int, timespec const*) + 220
2   org.qt-project.QtCore             0x00000001121b971a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 810
3   org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
4   org.qt-project.QtCore             0x0000000111f9a063 QThread::exec() + 131
5   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
6   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
7   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 11:: QNetworkAccessManager thread
0   libsystem_kernel.dylib            0x00007fff67d2a3d6 poll + 10
1   org.qt-project.QtCore             0x00000001121b7eee qt_safe_poll(pollfd*, unsigned int, timespec const*) + 94
2   org.qt-project.QtCore             0x00000001121b971a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 810
3   org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
4   org.qt-project.QtCore             0x0000000111f9a063 QThread::exec() + 131
5   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
6   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
7   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 12:: QNetworkAccessManager thread
0   libsystem_kernel.dylib            0x00007fff67d2a3d6 poll + 10
1   org.qt-project.QtCore             0x00000001121b7f6c qt_safe_poll(pollfd*, unsigned int, timespec const*) + 220
2   org.qt-project.QtCore             0x00000001121b971a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 810
3   org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
4   org.qt-project.QtCore             0x0000000111f9a063 QThread::exec() + 131
5   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
6   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
7   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 13:: QNetworkAccessManager thread
0   libsystem_kernel.dylib            0x00007fff67d2a3d6 poll + 10
1   org.qt-project.QtCore             0x00000001121b7f6c qt_safe_poll(pollfd*, unsigned int, timespec const*) + 220
2   org.qt-project.QtCore             0x00000001121b971a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 810
3   org.qt-project.QtCore             0x00000001121570d7 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 471
4   org.qt-project.QtCore             0x0000000111f9a063 QThread::exec() + 131
5   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
6   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
7   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 14:: Thread (pooled)
0   libsystem_kernel.dylib            0x00007fff67d26882 __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff67de7425 _pthread_cond_wait + 698
2   org.qt-project.QtCore             0x0000000111fa2f50 0x111f79000 + 171856
3   org.qt-project.QtCore             0x0000000111fa2c7e 0x111f79000 + 171134
4   org.qt-project.QtCore             0x0000000111fa2bd3 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83
5   org.qt-project.QtCore             0x0000000111f9f4b5 0x111f79000 + 156853
6   org.qt-project.QtCore             0x0000000111f9af79 0x111f79000 + 139129
7   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
8   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 15:
0   libsystem_pthread.dylib           0x00007fff67de2b68 start_wqthread + 0

Thread 16:
0   libsystem_pthread.dylib           0x00007fff67de2b68 start_wqthread + 0

Thread 17:
0   libsystem_kernel.dylib            0x00007fff67d2c0fe __select + 10
1                                     0x000000010ed081f9 INDI::BaseClientPrivate::listenINDI() + 1097
2                                     0x000000010ed0b0be 0x10e2a1000 + 10920126
3   libsystem_pthread.dylib           0x00007fff67de7109 _pthread_start + 148
4   libsystem_pthread.dylib           0x00007fff67de2b8b thread_start + 15

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0xca3a3d09ec60002e  rbx: 0x8000000000000000  rcx: 0x8000000000000000  rdx: 0x8000000000000000
  rdi: 0x8000000000000000  rsi: 0x8000000000000000  rbp: 0x00007ffee195cba0  rsp: 0x00007ffee195cba0
   r8: 0x00000000000001ff   r9: 0x00000000000007fb  r10: 0x00000000000018a0  r11: 0x0000000000000020
  r12: 0x00006000038c1730  r13: 0x0000600001e5c360  r14: 0x00007ffee195cc38  r15: 0x000060000337e3f0
  rip: 0x00007fff67dd8e52  rfl: 0x0000000000010286  cr2: 0x00000001112f0515
  
Logical CPU:     1
Error Code:      0x00000000
Trap Number:     13
2 years 5 months ago #76216

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Tried many times to get my Mac to connect to the INDIHUB server.  Each time the Mac version of Stars crashed as soon as it connected.
Here's what the INDIHUB server on the remote Stellarmate displayed.

stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos-INDIHUB -indi-server-manager=localhost:8624 -mode=share -api-port=8787
2021/10/01 14:17:41 Connection to local INDI-Server Manager on localhost:8624...
2021/10/01 14:17:41 ...OK
2021/10/01 14:17:41 INDI-server is running with active INDI-profile 'NMCosmos-INDIHUB'
2021/10/01 14:17:41 INDIDrivers:
2021/10/01 14:17:41 {Binary:indi_astrometry Skeleton:<nil> Family:Auxiliary Label:Astrometry Version:0.1 Role: Custom:false Name:Astrometry}
2021/10/01 14:17:41 {Binary:indi_asi_ccd Skeleton:<nil> Family:CCDs Label:ZWO CCD Version:2.0 Role: Custom:false Name:ZWO CCD}
2021/10/01 14:17:41 {Binary:indi_nexdome Skeleton:<nil> Family:Domes Label:NexDome Version:1.6 Role: Custom:false Name:NexDome}
2021/10/01 14:17:41 {Binary:indi_asi_wheel Skeleton:<nil> Family:Filter Wheels Label:ASI EFW Version:2.0 Role: Custom:false Name:ASI EFW}
2021/10/01 14:17:41 {Binary:indi_sx_ccd Skeleton:<nil> Family:CCDs Label:SX CCD Version:1.15 Role: Custom:false Name:SX CCD}
2021/10/01 14:17:41 {Binary:indi_ioptronv3_telescope Skeleton:<nil> Family:Telescopes Label:iOptron CEM120 Version:1.4 Role: Custom:false Name:iOptronV3}
2021/10/01 14:17:41 {Binary:indi_aagcloudwatcher_ng Skeleton:<nil> Family:Weather Label:AAG Cloud Watcher NG Version:1.6 Role: Custom:false Name:AAG Cloud Watcher NG}
2021/10/01 14:17:41 Test connection to local INDI-Server on localhost:7624...
2021/10/01 14:17:41 ...OK
2021/10/01 14:17:41 Connecting to the indihub.space cloud...
2021/10/01 14:17:41 ...OK
2021/10/01 14:17:42 Current agent version: 1.0.6
2021/10/01 14:17:42 Access token: 048b2866ac37496880490a4a21f520ca
2021/10/01 14:17:42 Host session token: 912965dd061d4edfa16f2d47cf2f631d
2021/10/01 14:17:42 Starting INDI-Server in the cloud...
2021/10/01 14:17:42 ...OK

                                ************************************************************
                                *               INDIHUB public address list!!              *
                                ************************************************************
                                                                                            
                                   INDI-Server: node-1.indihub.io:52260
                                                                                            
                                ************************************************************

                                Please provide your guest with this information:

                                1. Public address list from the above
                                2. Focal length and aperture of your main telescope
                                3. Focal length and aperture of your guiding telescope
                                4. Type of guiding you use: PHD2 or guiding via camera
                                5. Names of your imaging camera and guiding cameras

                                NOTE: These public addresses will be available ONLY until
                                agent is running! (Ctrl+C will stop the session)

2021/10/01 14:19:29 Connecting to local INDI-Server... on localhost:7624
2021/10/01 14:19:29 ...OK
2021/10/01 14:19:30 Client closed connection 1 to the cloud, so closing it to local INDI-Server too
2021/10/01 14:19:30 Failed to receive a response from INDI-Server: read tcp 127.0.0.1:49052->127.0.0.1:7624: use of closed network connection
^C2021/10/01 14:20:18 Stopping API-server gracefully. OS signal received: interrupt

AT THIS POINT, I closed the session with CONTRL-C


2021/10/01 14:20:18 Closing share-session
                                ************************************************************
                                *               INDIHUB session finished!!                 *
                                ************************************************************
                                                                                            
                                   INDI-Server: node-1.indihub.io:52260 - CLOSED!!
                                                                                            
                                ************************************************************
2021/10/01 14:20:18 API-server was shutdown gracefully
stellarmate@stellarmate:~ $ 

Here's what I had entered into the Mac version of Kstars.  It looks fine to me.

 

Once I hit the connect button, KStars crashes to the desktop.  
 
2 years 5 months ago #76229
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.251 seconds