Summarize CI Server Setup and Security Guide, add the draft installation-security skill and tools/setup_check.ps1 (read-only check practiced on the test system), and log ISS-008/009. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
6 KiB
6 KiB
Issue register
Open questions and problems found while building the repo.
Status: open · investigating · closed
Item and station names such as AID.* come from the author's own test project on the
development system (see "Test system" in progress.md); they do not exist on other systems.
How to close an issue
- Confirm the answer with the user (practiced on the test system where possible).
- Update every file in the issue's "Update on close" column with the answer.
- Update the matching row in
knowledge/progress.md(status and notes). - Set the issue to closed and write the resolution and date in "Next step / resolution". Keep closed issues in the table as history.
Issues
| ID | Date | Area | Issue | Status | Next step / resolution | Update on close |
|---|---|---|---|---|---|---|
| ISS-001 | 2026-09-30 | ITEM (itmval) |
Writing an item with itmval -p -n AID.WRPS.SIM.INFLOW -v 400 added the uoff option flag (options 0x…8a → 0x…8e). The flag stayed after writing the original value back. Meaning of uoff unknown; not found in the EN manuals by text search. |
open | 2026-09-30: writing internal sample items (CI-Eng-Sample.*, no station) does not set uoff (options stay 0x…88), so it is tied to station-connected items (the AID item was already off, its station not communicating). Still to find: meaning and how to clear it (ITEM Service IM 36K10L35/L36, Engineering Module I/O Processes IM 36K10C10). Revisit in phase 5 with a station item. |
.claude/skills/system-management/tasks/read-write-item.md (replace the uoff note under "Read the current value"); knowledge/progress.md row "Write an item with itmval -p" |
| ISS-002 | 2026-09-30 | DATABASE (dsschk) |
dsschk -d ITEM_DF -v (check only) exits 0 with no console output and nothing new in umhlog.log. Where results are reported is unknown. |
closed | Closed 2026-09-30 (confirmed by user). 2026-09-30: dsschk -e -v prints a start/end line per dataset (228 checked, no problems) and logs to umhlog.log. Plain dsschk only compares copies between nodes, so it prints nothing on a single-node system. ismchk needs a database file name (usage: ismchk data_base_name), not run yet. |
Create .claude/skills/system-management/tasks/consistency-check.md and add it to that skill's SKILL.md; knowledge/manuals/IM36K10J10-01EN.md §4.1.1 consistency tools (add where output goes); knowledge/progress.md row "Consistency check" |
| ISS-003 | 2026-09-30 | DATABASE (dssqld) |
Filtered export (dssqld -e <out> <filter>.qli) failed with a guessed filter syntax (@ITEM_DF, @FIELD, @SELECT). |
closed | Closed 2026-09-30 (confirmed by user). 2026-09-30: the quick load data format is now known and verified (@LANGUAGE, @VERSION, @FIELDS, @<DATASET>, quoted CSV records, \ continuation, ! comments; IM 36K10L45 §9.11). Filter syntax found (IM 36K10L50 §3.6) and practiced, awaiting confirmation: a file with @SELECT, then the filter in single quotes (strings in double quotes), then @<DATASET>; run dssqld -e <out> <filter>.qli. ITEM_HISTORY returns nothing unless the filter names ITEM_NAME and a SAMPLE_TIME range (SAMPLE_TIME > "dd-mm-yyyy hh:mm:ss" and SAMPLE_TIME < ...). |
.claude/skills/system-management/tasks/export-dataset.md section "Filtered exports"; knowledge/manuals/IM36K10J10-01EN.md §5.6 step 1; knowledge/progress.md row "Export a dataset" |
| ISS-004 | 2026-09-30 | ITEM (itmval) |
itmval -g -a <1..5> returns ITM-E-WRONG_ATT on AID.WRPS.* items, so reading limits is unproven. |
closed | Closed 2026-09-30 (confirmed by user). On CI-Eng-Sample.TANK1.LEVEL (limits set) -a 1..5 returned deadband 0, low 20, high 80, low-low 10, high-high 90. The error only occurs on items without limits. |
.claude/skills/system-management/tasks/read-write-item.md (limits section); knowledge/progress.md row "Read an item with itmval -g" |
| ISS-005 | 2026-09-30 | DATABASE (dssqld) |
Loading 04_item_his_df.qli straight after creating the storage group gave 2 errors once; three other runs were clean. Error text not captured. |
open | Added a 5 s pause in load.cmd. If it happens again, capture 04_item_his_df.qlo. |
examples/CI-Eng-Sample/load.cmd; .claude/skills/system-management/tasks/load-remove-records.md |
| ISS-006 | 2026-09-30 | HISTORY (ithloahis) |
Samples dated before the start of the current storage unit were not stored (no error shown); samples after it were. Also, a new storage group stored nothing until CI Server was restarted. | open | Confirm with History Management (IM 36K10L20) in phase 9: how to load into older units, and whether a restart is really required. | .claude/skills/system-management/tasks/load-history.md; examples/CI-Eng-Sample/README.md; knowledge/manuals/IM36K10J10-01EN.md command-line tools |
| ISS-007 | 2026-09-30 | INTEGRATION (monitoring) | intdskmon wrote 61.9 for a C: drive that is 61.9 % used / 38.1 % free, although the manual says it monitors the disk free space rate. intspawn did nothing when the command path was ~130 characters; a short path worked (limit unknown). |
open | Confirm the disk value meaning and the path limit. | .claude/skills/system-management/tasks/monitoring-processes.md; knowledge/manuals/IM36K10J10-01EN.md §4.1.6; examples/CI-Eng-Sample/monitoring/ |
| ISS-008 | 2026-09-30 | ACCESS (web/OPC UA server?) | ci_start.log on the test system shows CppServerAPI::Run() failed: InitializeSslCtx(): SSL_CTX_use_certificate_chain_file() failed. right after ACCESS Service starts. Which component and certificate is not known. |
open | Identify in phase 7 (OPC Interface IM 36K10E20, Data Access IM 36K10L45). | .claude/skills/installation-security/tasks/setup-check.md; the phase 7 skill |
| ISS-009 | 2026-09-30 | Security Guide | DCOM port range printed as 20500–20550 in the firewall table but "2500–20550" in the OPC configuration table. Taken as a typo for 20500–20550. | open | Confirm on a system with IT security applied. | knowledge/manuals/IM36K01C30-01EN.md §4 |