Hi, Ross, > On Dec 18, 2020, at 10:39, Ross Andrew Donnachie <[email protected]> > wrote: > > Is it possible that backend code that doesn't enclose its shared memory > access (hput*() or hget*()) between hashpipe_status_un/lock_safe() would > cause semaphore errors? This could be reasonably deduced as logical as the > semaphore error occurred when reading from the hashpipe_status_buffer
The errors you showed earlier were data buffer related, not status buffer related... > On Dec 16, 2020, at 22:08, Ross Andrew Donnachie <[email protected]> > wrote: > > Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_set_filled): semctl error > [Invalid argument] > Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_wait_free_timeout): semop > error [Invalid argument] > semop: Invalid argument > Tue Dec 15 17:37:19 2020 : Error (hpguppi_atasnap_pktsock_thread): error > waiting for free databuf [Invalid argument] > Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_set_free): semctl error > [Invalid argument] > Tue Dec 15 17:37:19 2020 : Error (hashpipe_databuf_wait_filled_timeout): > semop error [Invalid argument] > semop: Invalid argument > Tue Dec 15 17:37:19 2020 : Error (hpguppi_atasnap_pkt_to_FTP_transpose): > error waiting for input buffer, rv: -2 [Invalid argument] That said, there was a bug fix made to the hget.c file last April in commit 75a9a17: https://github.com/david-macmahon/hashpipe/commit/75a9a17b52b265e8caf398640c410f8f0004ac8f <https://github.com/david-macmahon/hashpipe/commit/75a9a17b52b265e8caf398640c410f8f0004ac8f> This bug could cause corruption of values returned by hget functions iff any hget functions were used without locking the semaphore (e.g. if using hget functions on memory that isn't the status buffer even if it is only accessed by a single thread). Not sure whether this is related to the problem you're experiencing, but all Hashpipe installations should use this latest hget.c file. HTH, Dave -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/D6AD8FB0-8D0B-42BC-9794-523A21C1DB3F%40berkeley.edu.
