Server Log
The Server log page shows the end of the server log file, newest lines first, so an administrator can follow what the server does — a batch, a Peppol lookup, a failed transformation — without opening a shell on the host. Open it under Management → Server log; access is granted per role, like the other Management pages (see Roles).
At a glance
Controls
| Control | Effect |
|---|---|
| Tail | How much of the end of the file is read: 128 KB, 512 KB (default), 2 MB or 8 MB. When the file is larger, the status line says so — raise the tail to read further back. |
| Severity | Checkboxes ERROR, WARN, INFO (the three ticked by default), DEBUG and Unstructured — the lines that do not follow the ** LEVEL ** MODULE ** … : message form. |
| Module | List built from the modules seen in the lines read (PROCESS, UBL, PEPPOL…); All modules by default. |
| Search… | Case-insensitive text filter. |
| Auto-refresh | Reloads the tail every 5 seconds. |
| Refresh | Reloads the tail now. |
Stack traces stay attached to the line that threw them, so filtering on ERROR keeps the whole trace. The status line shows the file read, its size and how many lines are shown out of those scanned.
Which file is read
The page finds the file on its own: the launcher's nomaubl-<env>.log, or — on Linux — the file the server's output is redirected to. When the server runs under another launcher, set its path in Server log file in the global settings; left blank, the automatic detection applies. If no file can be found, the page says so and points to that setting.
Tips & best practices
- Start from
ERRORandWARN. UntickINFOto keep only what needs a look, then widen with the module list. - Follow a run with auto-refresh. Launch a batch or a scan, tick Auto-refresh and watch the lines come in.
- Raise the tail for an older event. The default 512 KB covers recent activity; switch to 2 MB or 8 MB to go further back.