| | 330 | JRF: Have been checking through the list of cluster nodes using neb-host to find nodes that have been left in repair. So that they can be brought back into production if they are ok |
| | 331 | |
| | 332 | There are config files located in the modules folder that dictate which nodes to save results do. e.g. processing of files relating to GPC1 XY01 get saved to ipp067.0. The current config is found here: |
| | 333 | {{{ |
| | 334 | /data/ippc64.1/ippitc/psconfig/ipp-20170121.lin64/share/pantasks/modules |
| | 335 | }}} |
| | 336 | Best practice is to make a backup in the folder. MEH handled the changes to this file. |
| | 337 | |
| | 338 | To use the new config need to stop and shutdown stdscience pantasks. Make sure that there are no jobs still running after stopping before you shutdown. |
| | 339 | |
| | 340 | Then to restart with the new config go to the machine that was running pantasks and run: |
| | 341 | {{{ |
| | 342 | ./start_server.sh stdscience |
| | 343 | }}} |
| | 344 | This will start pantasks back up, AND it archives the log (which does not happen if you start it normally). |
| | 345 | |
| | 346 | With pantasks running we need to actually get the scheduler and controller going by using the following commands: |
| | 347 | {{{ |
| | 348 | server input input |
| | 349 | setup |
| | 350 | run |
| | 351 | }}} |
| | 352 | |
| | 353 | |
| | 354 | JRF: Going back to the ippmonitor issues: |
| | 355 | There were a lot of LAP chip errors, which look like an improper state. These just need to have the chip updated e.g. |
| | 356 | {{{ |
| | 357 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ps_ud_WEB -chip_id XXXXXX |
| | 358 | }}} |
| | 359 | |
| | 360 | |