After an update to 3.0 demmaccs-processor stopped processing S2-Data (it works for Landsat8 now)
I use a local root with symlinks to get the Level1-Data from an archive.
Main error:
–docker-image-maja sen4x/maja:3.2.2-centos-el info finished with return code 126 in 0:00:00.33805
Can NOT run MAJA script, error code: 1
Could not read maja log at /mnt/archivR022_T33UWP_20181105T104758.SAFE/maja.log
full-log here:
sen2agri-demmaccs.service - Runs MACCS on L1C products
Loaded: loaded (/usr/lib/systemd/system/sen2agri-demmaccs.service; static; vendor preset: disabled)
Active: active (running) since Thu 2022-01-13 15:21:58 UTC; 1min 34s ago
Main PID: 17730 (python2)
Tasks: 5
Memory: 477.8M
CGroup: /system.slice/sen2agri-demmaccs.service
└─17730 python2 /usr/share/sen2agri/sen2agri-demmaccs/l2a_launcher.py
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Running L2a Processors, console outputSIL2A_20181105T101211_N0206_R022_T33UWP_20181105T104758.SAFE/l2a_14019.log
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Command docker run -v /var/run/docker.7 -v /etc/localtime:/etc/localtime -v /usr/share/zoneinfo:/usr/share/zoneinfo -v /mnt/archive/srtm:/mnt/archive/srtm -vja/UserConfiguration:/mnt/archive/gipp_maja/UserConfiguration -v /mnt/archive/gipp_maja:/mnt/archive/gipp_maja -v /mnt/hive/demmaccs_tmp/archives/tmppgNAFO/S2A_MSIL1C_20181105T101211_N0206_R022_T33UWP_20181105T104758.SAFE:/mnt/archive/dem6_R022_T33UWP_20181105T104758.SAFE -v /mnt/archive/maccs_def/uwp/l2a/output/S2A_MSIL2A_20181105T101211_N0206_R022_T33UW/S2A_MSIL2A_20181105T101211_N0206_R022_T33UWP_20181105T104758.SAFE --name l2a_processors_14019_I4JUIL0E sen4x/l2a-proceve/srtm --swbd /mnt/archive/swbd --conf /mnt/archive/gipp_maja/UserConfiguration --processes-number-dem 1 --processes-nr /mnt/archive/demmaccs_tmp/ --delete-temp --product-id 14019 /mnt/archive/demmaccs_tmp/archives/tmppgNAFO/S2A_MSIL1C_2rchive/maccs_def/uwp/l2a/output/S2A_MSIL2A_20181105T101211_N0206_R022_T33UWP_20181105T104758.SAFE --tiles-to-process 33ge-l8align sen4x/l2a-l8-alignment:0.1 --docker-image-dem sen4x/l2a-dem:0.1 --docker-image-maja sen4x/maja:3.2.2-centos-el info finished with return code 126 in 0:00:00.338057
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Can NOT run MAJA script, error code: 1
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Successful processing = False
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Invalid output format.
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Could not read maja log at /mnt/archivR022_T33UWP_20181105T104758.SAFE/maja.log
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 0> Valid L2a product = False
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <master> Product 14019 was processed with errors,
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 1> Successful pre-processing = True
Jan 13 15:22:24 sen4cap-v2-25062021.novalocal l2a_launcher.py[17730]: <worker 1> Running L2a Processors, console outputSIL2A_20181104T095159_N0206_R079_T33UWP_20181104T120209.SAFE/l2a_14018.log
Anyone an idea what happens here? Seems that there is a problem with the path to the log-file? @cudroiu
Actually, the log error is not the cause but a consequence of a previous error. We shall update the text of the error, as it should say: can not determine the precise error since no maja log was written.
Anyway, I tried to look at the logs you sent. However, I think there is a problem with their rendering. For example, I can see -v /var/run/docker.7 where it should have been -v /var/run/docker.sock:/var/run/docker.sock
Thus, could you please provide the log files, which you will find in /var/log/sen2agri/, i.e. l2a_launcher.log and l2a_14019.log; Also, could you state the values of all database parameters starting with processor.l2a. from config table.
There is a permission issue while docker tries to mount some temporary/working files, see below an extract from l2a_14681.log:
/usr/bin/docker-current: Error response from daemon: error while creating mount source path '/mnt/archive/demmaccs_tmp/archives/tmpK49g7h/S2B_MSIL1C_20210505T100029_N0300_R122_T33UXP_20210505T123835.SAFE': mkdir /mnt/archive/demmaccs_tmp/archives/tmpK49g7h/S2B_MSIL1C_20210505T100029_N0300_R122_T33UXP_20210505T123835.SAFE: permission denied.
Please do check the permissions for /mnt/archive/demmaccs_tmp/, the user sen2agri-service should be able to read and write. Also, If there any folders within demmaccs_tmp, they should be removed, or at least make sure that sen2agri-service user is able to remove them.
hm I checked everything and the user sen2agri-service is able to write to and read in /mnt/archive/demaccs_tmp. In fact it’s the owner of the directory:
I can also copy and delete file to the archive logged in as user sen2agri-service. And what is also strange is that the landsat scence are downloaded and processed but sentinel-2 scenes stuck somewhere.
Could the problem be that I’m using symlinks pointing to my localroot directory and the migration to a docker environment from version 2 to version 3 doesn’t support this?