Sean Flanagan

Can we also add the **username** that the mdsip session belongs to into the `.errors` log? Trying to associate an error message with the user that produced it is currently...

There's likely more to this than open files, as enabling core dumps against the `systemd` services running the "disaptcher" (i.e. `mdsip -s` on `atlas:8002`) and the "mdsloader" (i.e. `mdsip -s`...

EDIT: Note that as of the time the following `lsof` was pulled, those **PIDs** are for: - dispatcher: systemd service `mds-8002` on pid `3730021` - mdsloader: systemd service `mds-8003` on...

Systemd contents: mds-8002 ``` [Unit] Description=MDSplus Dispatcher Service After=network.target [Service] User=mdsadmin Type=simple LimitNOFILE=64000 LimitCORE=infinity ExecStart=/usr/local/mdsplus/bin/mdsipd-dispatching 8002 -block [Install] WantedBy=multi-user.target ``` mds-8003: ``` [Unit] Description=MDSplus Loader Service After=network.target [Service] Type=simple LimitNOFILE=64000...

Assuming, as an upper bound, that everything is enabled and ops is having a long and/or productive run day... > How many "actions" are issued when running a single DIII-D...

> Let me know if you have any problems with the systemd workaround on GA's server. I redesigned my `mds-8002` systemd file to add: ``` User=mdsadmin Restart=always ExecStartPost=/usr/local/mdsplus/local/mds-8002-post.sh ``` Where...

Regarding the ongoing attempts to fix the original issue in this thread... As of build alpha_release-7-139-52 ... The IDL API cannot open trees: ``` IDL> mdsconnect,'atlas.gat.com' % Compiled module: MDSCONNECT....

Python reverts are looking good: ``` >>> import MDSplus >>> c = MDSplus.Connection('atlas.gat.com') >>> c.openTree('nb',190000) >>> data = c.get('\PINJ') >>> print,data.data() (, array([0., 0., 0., ..., 0., 0., 0.], dtype=float32))...

@mwinkel-dev I reread the `.txt` file and now recognize the difference between our tests: - Sean's test: `set_database`, `mdsconnect` - Mark's test: `set_database`, `mdsconnect`, `set_database` There are `dsql` calls in...

> Please repeat your tests, but do not use print or help to examine !MDS_SOCKET and !MDSDB_SOCKET. And let Stephen and me know if the database proxy remains intact after...