ID |
Date |
Author |
Topic |
Subject |
Text |
|
1048
|
17 Mar 2015 |
Wes Gohn | Forum | PosgresQL | For our MIDAS installation at Fermilab, it
is necessary that we be able to write to
a PosgresQL
|
|
1083
|
29 Jul 2015 |
Wes Gohn | Forum | error | SIGSEGV is a segmentation fault. Most often
it means some ODB parameter is out of bounds
or there is
|
|
1088
|
10 Aug 2015 |
Wes Gohn | Forum | bk_create change | After pulling the newest version of midas,
our compilation would fail on
bk_create, with the error:
|
|
1175
|
22 Apr 2016 |
Wes Gohn | Bug Report | Calling external script from sequencer | Can the MIDAS Sequencer call an external script?
It seems that it should be able to. I have
a simple
|
|
1176
|
22 Apr 2016 |
Wes Gohn | Bug Report | Calling external script from sequencer | Nevermind. I just had to give it a path to
my script. Now it's fine.
|
|
1193
|
07 Sep 2016 |
Wes Gohn | Forum | ODB as JSON file | Hi. Is it currently possible to automatically
save the MIDAS ODB as a JSON file?
I can do it manually in odbedit, but it looks |
|
1201
|
26 Sep 2016 |
Wes Gohn | Info | mongoose v6.4 is ready for use | Since updating to the most recent midas commit,
we get the following error if we try running
mhttpd without su privileges:
|
|
1261
|
14 Apr 2017 |
Wes Gohn | Forum | mhttpd lag | Hi everyone,
We have recently been experiencing a lot |
|
1309
|
27 Jul 2017 |
Wes Gohn | Suggestion | Increasing Max Number of Frontends | Below are the steps we used to increase the
maximum number of frontends that we could
run.
|
|
1382
|
21 Aug 2018 |
Wes Gohn | Bug Report | mserver problem | Hi. We've just updated our midas installation
to the newest version, and we now see repeated
errors from the
|
|
846
|
14 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | I've been trying to set up midas to create
an automatic elog entry at the end of
each run and I've run into a problem. I've |
|
848
|
17 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | > > I've been trying to set up midas to create
an automatic elog entry at the end of
> > each run and I've run into a problem. |
|
1597
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | I wrote a c++ frontend to read data from CAEN
VX1730 digitizers which is used in
parallel with the GRIFFIN frontend to read |
|
1601
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > run the frontend inside gdb and post the
stack trace after the crash?
>
|
|
1603
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > run the frontend inside gdb and post
the stack trace after the crash?
> > >
|
|
1605
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > >
> > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
1608
|
10 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > >
> > > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
1613
|
11 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > ... finding a current midas.log file
>
> On the "help" page, see "midas.log".
|
|
1680
|
08 Sep 2019 |
Vinzenz Bildstein | Bug Report | https redirect and ODB access | I'm not sure if these issues are related or
not, but I'm getting an error
message when I want to access the root of |
|
1728
|
21 Oct 2019 |
Vinzenz Bildstein | Forum | Data for key truncated | I keep on getting messages like this:
16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR] |
|