Troubleshooting¶
This page lists several commonly seen issues and how to address them.
OSError: Missing data mappings¶
The wis2box logging displays the error:
OSError: Missing data mappings: [Errno 2] No such file or directory: '/data/wis2box/data-mappings.yml'
Check wis2box.env
and check value that was set for WIS2BOX_HOST_DATADIR
WIS2BOX_HOST_DATADIR=/home/wmouser/wis2box-data
In this case the value set was ‘/home/wmouser/wis2box-data’
Check that the file ‘data-mappings.yml’ is contained in this directory:
ls -lh /home/wmouser/wis2box-data/data-mappings.yml
After you have ensured the data-mappings.yml is in the directory defined by WIS2BOX_HOST_DATADIR, restart the wis2box:
python3 wis2box-ctl.py stop
python3 wis2box-ctl.py start
Topic Hierarchy validation error: Unknown file type¶
Check data-mappings.yml
file to adjust the file extension expected by the plugins processing your dataset.
If you are ingesting files with extension .bin:
plugins:
bin:
- plugin: wis2box.data.bufr4.ObservationDataBUFR
notify: true
buckets:
- ${WIS2BOX_STORAGE_INCOMING}
file-pattern: '*'
If you are ingesting files with extension .b
:
plugins:
b:
- plugin: wis2box.data.bufr4.ObservationDataBUFR
notify: true
buckets:
- ${WIS2BOX_STORAGE_INCOMING}
file-pattern: '*'
The Access Key Id you provided does not exist in our records¶
If you see this error when uploading data to the wis2box-incoming storage, you have provided the wrong username and/or password to access MinIO.
Check the values for WIS2BOX_STORAGE_USERNAME
and WIS2BOX_STORAGE_PASSWORD
set in the wis2box.env
file.
Topic Hierarchy validation error: No plugins for … in data mappings¶
A file arrived a folder for which no matching dataset was defined in data-mappings.yml
.
For dataset foo.bar
, store your file in the path /foo/bar/
.
This requires either updating data-mappings.yml
or changing the target folder under which the file is received.
ERROR - Failed to publish, wsi: …, tsi: XXXXX¶
Data arrived for a station that is not present in the station metadata cache.
To add missing stations, use the station-editor in wis2box-webapp (from wis2box-1.0b5) or update the file metadata/station/station_list.csv
in the wis2box data directory and run the command:
python3 wis2box-ctl.py login
wis2box metadata stations publish-collections
Error: no such container: wis2box-management¶
If the wis2box-management container is not running, the login
command will fail.
The wis2box-management container depends on other services being available before it can successfully started.
Please check all services are Running using the following command:
python3 wis2box-ctl.py status
Possible issues are:
The host ran out of diskspace, check the output of
df -h
and ensure there is sufficient space availableThe directory defined by
WIS2BOX_HOST_DATADIR
does not contain the filedata-mappings.yml
or the file is invalidThe directory defined by
WIS2BOX_HOST_DATADIR
does not contain the filemetastation/station/station_list.csv
or the file is invalidWIS2BOX_STORAGE_PASSWORD
is too short, MinIO will fail to start if you specify aWIS2BOX_STORAGE_PASSWORD
of less than 8 characters
wisbox-UI is empty¶
If when you access the wis2box UI you see the interface but no datasets are visible; check the WIS2BOX_URL
and WIS2BOX_API_URL
are set correctly.
Please note that after changing the WIS2BOX_URL
and WIS2BOX_API_URL
, you will have to restart wis2box:
python3 wis2box-ctl.py stop
python3 wis2box-ctl.py start
..and then repeat the commands for adding your dataset and publishing your metadata, to ensure the URLs are updated in the records accordingly:
python3 wis2box-ctl.py login
wis2box data add-collection /data/wis2box/metadata/discovery/metadata-synop.yml
wis2box metadata discovery publish /data/wis2box/metadata/discovery/metadata-synop.yml