SEADAS errors for Windows/Docker

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
aleesumner
Posts: 5
Joined: Fri Feb 02, 2024 2:30 pm America/New_York
Answers: 0

Re: SEADAS errors for Windows/Docker

by aleesumner » Mon Feb 12, 2024 9:38 am America/New_York

Aynur,
Update: I got the processors to download. I tried to geolocate a MODIS level 1 file to test whether the processors were working. I got the error shown below, which is slightly different for Docker or VirtualMachine processor ___location. I still have the same errors showing in the Software & System Info, so I think this may be tied to that. The class starts tomorrow. I hope to get it working before then but I will notify the instructors if not. It seems there was trouble with the system in one of the previous SeaDas courses and they extended the homework deadline, so I am hoping this course will do the same. Thanks for your continued help!

Processor Location Docker:
execution exception: java.io.IOException: modis_GEO failed with exit code 1.
Check log for more details.
Error! dump_metadata failed.

In Docker Log:
2024-02-12 06:21:57 server ocssw root path: /root/ocssw/bin
2024-02-12 06:21:57 .netrc in seadasClientServer true
2024-02-12 06:21:57 .netrc in home dir true
2024-02-12 06:22:59 /root/ocssw/bin/ocssw_runner --ocsswroot /root/ocssw modis_GEO /root/seadasClientServerShared/ --output=/root/seadasClientServerShared/A2017284195500.GEO --verbose process status on server = -100
2024-02-12 06:22:59 server process observer: 6402
2024-02-12 06:22:59 server process observer: 6403
2024-02-12 06:23:01 final process status: 1
2024-02-12 06:23:01 final process status: 1

Processor Location Virtual Machine:
execution exception: java.io.IOException: modis_GEO failed with exit code 1.
Check log for more details.
Error! dump_metadata failed.
Can't find input file '/root/seadasClientServerShared/'.

2024-02-12 06:28:47 server ocssw root path: /root/ocssw/bin
2024-02-12 06:28:47 .netrc in seadasClientServer true
2024-02-12 06:28:47 .netrc in home dir true
2024-02-12 06:29:13 /root/ocssw/bin/ocssw_runner --ocsswroot /root/ocssw modis_GEO /root/seadasClientServerShared/ --output=/root/seadasClientServerShared/A2017284195500.GEO --verbose process status on server = -100
2024-02-12 06:29:13 server process observer: 6402
2024-02-12 06:29:13 server process observer: 6403
2024-02-12 06:29:14 final process status: 1
2024-02-12 06:29:14 final process status: 1

Filters:

OB SeaDAS - aynur
Subject Matter Expert
Subject Matter Expert
Posts: 64
Joined: Tue Dec 20, 2011 12:28 pm America/New_York
Answers: 0
Been thanked: 1 time

Re: SEADAS errors for Windows/Docker

by OB SeaDAS - aynur » Mon Feb 12, 2024 10:11 am America/New_York

There might be a problem with the connection. Can you check if you have a local firewall preventing web connections from python scripts?
mwraenqual wrote: Mon Feb 05, 2024 2:20 pm America/New_York Hello. I also am preparing for an upcoming workshop and having errors from SeaDAS 8.4.1 install on a PC (Windows 11). I tried to follow the video showing how to Install a SeaDAS processor. I get the following error:

ocssw installation script failed to download.
Please check network connection or 'seadas.ocssw.root' variable in the "seadas.config" file.
possible cause of error: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

mwraenqual
Posts: 13
Joined: Mon Feb 05, 2024 2:14 pm America/New_York
Answers: 0
Has thanked: 5 times

Re: SEADAS errors for Windows/Docker

by mwraenqual » Mon Feb 12, 2024 11:05 am America/New_York

I'm able to run a Python script that allows me to download content from urs.earthdata.nasa.gov. So, I don't believe the issue is with the firewall.

OB SeaDAS - aynur wrote:
> There might be a problem with the connection. Can you check if you have a
> local firewall preventing web connections from python scripts?
>
> [quote=mwraenqual post_id=17928 time=1707160826 user_id=8511]
> Hello. I also am preparing for an upcoming workshop and having errors from
> SeaDAS 8.4.1 install on a PC (Windows 11). I tried to follow the video
> showing how to Install a SeaDAS processor. I get the following error:
>
> ocssw installation script failed to download.
> Please check network connection or 'seadas.ocssw.root' variable in the
> "seadas.config" file.
> possible cause of error: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target
> [/quote]

mwraenqual
Posts: 13
Joined: Mon Feb 05, 2024 2:14 pm America/New_York
Answers: 0
Has thanked: 5 times

Re: SEADAS errors for Windows/Docker

by mwraenqual » Mon Feb 12, 2024 3:43 pm America/New_York

Is it possible that it is a Java issue?

mwraenqual wrote:
> I'm able to run a Python script that allows me to download content from
> urs.earthdata.nasa.gov. So, I don't believe the issue is with the firewall.
>
> OB SeaDAS - aynur wrote:
> > There might be a problem with the connection. Can you check if you have a
> > local firewall preventing web connections from python scripts?
> >
> > [quote=mwraenqual post_id=17928 time=1707160826 user_id=8511]
> > Hello. I also am preparing for an upcoming workshop and having errors from
> > SeaDAS 8.4.1 install on a PC (Windows 11). I tried to follow the video
> > showing how to Install a SeaDAS processor. I get the following error:
> >
> > ocssw installation script failed to download.
> > Please check network connection or 'seadas.ocssw.root' variable in the
> > "seadas.config" file.
> > possible cause of error: PKIX path building failed:
> > sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> > valid certification path to requested target
> > [/quote]

kh11block3_2
Posts: 1
Joined: Tue Feb 13, 2024 11:51 am America/New_York
Answers: 0

Re: SEADAS errors for Windows/Docker

by kh11block3_2 » Tue Feb 13, 2024 12:16 pm America/New_York

Hello,

I also signed up for the ARSET course and am having the same issue, however I am on Windows 11.

After following the Windows/Docker setup instructions already linked, I can load the 'Install/Update SeaDAS Processors' GUI window, but selecting any (or no) processor options leads to this error;

>
execution exception: java.io.IOException: install_ocssw failed with exit code 1.
Check log for more details.
Traceback (most recent call last):
File "/tmp/install_ocssw", line 1004, in <module>
sys.exit(run())
File "/tmp/install_ocssw", line 670, in run
downloadBundleList(options1[0])
File "/tmp/install_ocssw", line 271, in downloadBundleList
checkTag(options)
File "/tmp/install_ocssw", line 172, in checkTag
if not mf.check_tag(manifest_options, None):
File "/tmp/manifest.py", line 597, in check_tag
for tag in get_tags(options, args):
File "/tmp/manifest.py", line 568, in get_tags
status = httpdl(host, request, localpath=tempDir.name,
File "/tmp/manifest.py", line 100, in httpdl
with closing(obpgSession.get(urlStr, stream=True, timeout=timeout, headers=headers)) as req:
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 546, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 519, in request
prep = self.prepare_request(req)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 449, in prepare_request
auth = get_netrc_auth(request.url)
File "/usr/lib/python3/dist-packages/requests/utils.py", line 203, in get_netrc_auth
_netrc = netrc(netrc_path).authenticators(host)
File "/usr/lib/python3.8/netrc.py", line 30, in __init__
self._parse(file, fp, default_netrc)
File "/usr/lib/python3.8/netrc.py", line 39, in _parse
toplevel = tt = lexer.get_token()
File "/usr/lib/python3.8/shlex.py", line 109, in get_token
raw = self.read_token()
File "/usr/lib/python3.8/shlex.py", line 140, in read_token
nextchar = self.instream.read(1)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte
>

Docker Details show everything working up until this SeaDAS error:

>
argument: ocsswserver.config
2024-02-13 16:56:47 -- listing properties --
2024-02-13 16:56:47 processErrorStreamPortNumber=6403
2024-02-13 16:56:47 java.runtime.name=Java(TM) SE Runtime Environment
2024-02-13 16:56:47 sun.boot.library.path=/root/jre1.8.0_321/lib/amd64
2024-02-13 16:56:47 java.vm.version=25.321-b07
2024-02-13 16:56:47 java.vm.vendor=Oracle Corporation
2024-02-13 16:56:47 java.vendor.url=http://java.oracle.com/
2024-02-13 16:56:47 path.separator=:
2024-02-13 16:56:47 java.vm.name=Java HotSpot(TM) 64-Bit Server VM
2024-02-13 16:56:47 file.encoding.pkg=sun.io
2024-02-13 16:56:47 user.country=US
2024-02-13 16:56:47 sun.java.launcher=SUN_STANDARD
2024-02-13 16:56:47 sun.os.patch.level=unknown
2024-02-13 16:56:47 java.vm.specification.name=Java Virtual Machine Specification
2024-02-13 16:56:47 user.dir=/root
2024-02-13 16:56:47 java.runtime.version=1.8.0_321-b07
2024-02-13 16:56:47 java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
2024-02-13 16:56:47 java.endorsed.dirs=/root/jre1.8.0_321/lib/endorsed
2024-02-13 16:56:47 os.arch=amd64
2024-02-13 16:56:47 java.io.tmpdir=/tmp
2024-02-13 16:56:47 line.separator=
2024-02-13 16:56:47
2024-02-13 16:56:47 java.vm.specification.vendor=Oracle Corporation
2024-02-13 16:56:47 os.name=Linux
2024-02-13 16:56:47 sun.jnu.encoding=ANSI_X3.4-1968
2024-02-13 16:56:47 java.library.path=/usr/java/packages/lib/amd64:/usr/lib...
2024-02-13 16:56:47 java.specification.name=Java Platform API Specification
2024-02-13 16:56:47 java.class.version=52.0
2024-02-13 16:56:47 sun.management.compiler=HotSpot 64-Bit Tiered Compilers
2024-02-13 16:56:47 os.version=5.15.133.1-microsoft-standard-WSL2
2024-02-13 16:56:47 user.home=/root
2024-02-13 16:56:47 user.timezone=
2024-02-13 16:56:47 ocsswrest.version=1.0
2024-02-13 16:56:47 java.awt.printerjob=sun.print.PSPrinterJob
2024-02-13 16:56:47 file.encoding=ANSI_X3.4-1968
2024-02-13 16:56:47 java.specification.version=1.8
2024-02-13 16:56:47 ocsswroot=/root/ocssw
2024-02-13 16:56:47 user.name=root
2024-02-13 16:56:47 java.class.path=seadas-ocsswserver.jar
2024-02-13 16:56:47 keepIntermediateFilesOnServer=false
2024-02-13 16:56:47 java.vm.specification.version=1.8
2024-02-13 16:56:47 processInputStreamPortNumber=6402
2024-02-13 16:56:47 sun.arch.data.model=64
2024-02-13 16:56:47 java.home=/root/jre1.8.0_321
2024-02-13 16:56:47 sun.java.command=seadas-ocsswserver.jar ocsswserver.co...
2024-02-13 16:56:47 java.specification.vendor=Oracle Corporation
2024-02-13 16:56:47 user.language=en
2024-02-13 16:56:47 awt.toolkit=sun.awt.X11.XToolkit
2024-02-13 16:56:47 java.vm.info=mixed mode
2024-02-13 16:56:47 java.version=1.8.0_321
2024-02-13 16:56:47 java.ext.dirs=/root/jre1.8.0_321/lib/ext:/usr/java/...
2024-02-13 16:56:47 clientServerSharedDir=true
2024-02-13 16:56:47 sun.boot.class.path=/root/jre1.8.0_321/lib/resources.jar:...
2024-02-13 16:56:47 java.vendor=Oracle Corporation
2024-02-13 16:56:47 file.separator=/
2024-02-13 16:56:47 java.vendor.url.bug=http://bugreport.sun.com/bugreport/
2024-02-13 16:56:47 baseUriPortNumber=6400
2024-02-13 16:56:47 sun.cpu.endian=little
2024-02-13 16:56:47 sun.io.unicode.encoding=UnicodeLittle
2024-02-13 16:56:47 serverWorkingDirectory=/root/seadasClientServerShared
2024-02-13 16:56:47 sun.cpu.isalist=
2024-02-13 16:56:47 server ocssw root path: /root/ocssw/bin
2024-02-13 16:56:47 .netrc in seadasClientServer true
2024-02-13 16:56:47 .netrc in home dir true
2024-02-13 16:56:49 ORS is starting at
2024-02-13 16:56:49 Feb 13, 2024 3:56:49 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
2024-02-13 16:56:49 WARNING: A provider java.io.InputStream registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider java.io.InputStream will be ignored.
2024-02-13 16:56:49 Feb 13, 2024 3:56:49 PM org.glassfish.grizzly.http.server.NetworkListener start
2024-02-13 16:56:49 INFO: Started listener bound to [0.0.0.0:6400]
2024-02-13 16:56:49 Feb 13, 2024 3:56:49 PM org.glassfish.grizzly.http.server.HttpServer start
2024-02-13 16:56:49 INFO: [HttpServer] Started.
2024-02-13 16:56:49 Jersey new app started with WADL available at http://0.0.0.0:6400/ocsswws/application.wadl
2024-02-13 16:56:49 Press 'Ctrl' + 'C' to stop it...
2024-02-13 17:02:14 server ocssw root path: /root/ocssw/bin
2024-02-13 17:02:14 .netrc in seadasClientServer true
2024-02-13 17:02:14 .netrc in home dir true
2024-02-13 17:04:10 /tmp/install_ocssw --install_dir=/root/ocssw --avhrr --czcs --goci --hawkeye --hico --meris --modisa --modist --mos --msis2a --msis2b --ocm1 --ocm2 --octs --olcis3a --olcis3b --olil8 --olil9 --osmi --seawifs --sgli --viirsn --viirsj1 --viirsj2 --viirsdem --tag=T2023.24 --seadas process status on server = -100
2024-02-13 17:04:10 server process observer: 6402
2024-02-13 17:04:10 server process observer: 6403
2024-02-13 17:04:12 final process status: 1
2024-02-13 17:04:12 final process status: 1
>

For additional context;
- SeaDAS 8.4.1 (x64 for Windows)
- Docker Image 'seadas/ocssw-run1.2' (I noticed that there was also a 1.3 and 1.4, but I did not try these as they were not specified in the setup documentation(s)
- .netrc and .urscookies were created via (https://oceancolor.gsfc.nasa.gov/data/download_methods/?tab=download-methods-tab#netrc) through Windows Powershell as the perl .pl script that was also suggested (https://wiki.earthdata.nasa.gov/display/EL/Create+Your+.netrc+File) wasn't immediately available to run on my computer.
- My EarthData username features '_' in the name, though that might be notable as the documentations suggested that some special characters can cause problems, i.e. ! or ?, but doesn't mention '_'. I can't recall if the .netrc file is also case-sensitive.
- Windows 11 has this weird idea of making the root/home folder of a username truncated, i.e. 'Username' appears as 'usern', even though the folder is named otherwise correctly. Could this be impacting finding the correct files?

I'm happy to answer any further questions that might help troubleshoot what went wrong, as I realise I'm not the best versed with virtual machines and the scripting/coding required to setup.
Thank you.

aleesumner
Posts: 5
Joined: Fri Feb 02, 2024 2:30 pm America/New_York
Answers: 0

Re: SEADAS errors for Windows/Docker

by aleesumner » Tue Feb 13, 2024 4:53 pm America/New_York

Hi Aynur,
Not sure if this is helpful in resolving my error. I still have initial software/system error I started this post thread with, but have since been able to download the processors, but they're not working. During class, it was recommended to try to start SeaDas through the terminal, because it can improve how it works. When I did this, I got the following info in the terminal:
PS C:\Users\alees> & 'C:\Program Files (x86)\SeaDAS\bin\seadas64'
PS C:\Users\alees>

The launcher has determined that the parent process has a console and will reuse it for its own console output.
Closing the console will result in termination of the running program.
Use '--console suppress' to suppress console output.
Use '--console new' to create a separate console window.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.netbeans.ProxyURLStreamHandlerFactory (file:/C:/Program%20Files%20(x86)/SeaDAS/platform/lib/boot.jar) to field java.net.___URL.handler
WARNING: Please consider reporting this to the maintainers of org.netbeans.ProxyURLStreamHandlerFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
command is: [Ljava.lang.String;@74215c1b
command is: [Ljava.lang.String;@1199557f

The final lines provide the same info as the software/system info error. I have tried searching Earth Data Forum for other leads. Not sure if this is helpful either, but one previous thread recommended some code in Docker, which I ran and got the following:

# /root/ocssw/bin/ocssw_runner --ocsswroot /root/ocssw seadas_info
NASA Science Processing (OCSSW):
OCSSWROOT=/root/ocssw
OCDATAROOT=/root/ocssw/share
l2gen version: msl12 9.6.0-V2023.3 (Oct 4 2023 22:27:24)
l2bin version: 7.0.4
l3bin version: 5.13
l3mapgen version: l3mapgen 2.3.0-V2023.3 (Oct 4 2023 22:26:56)
Installed Missions: ['hawkeye', 'aqua', 'terra', 'olil8', 'olil9', 'viirsn', 'viirsj1', 'viirsj2']

General System and Software:
Operating system: Ubuntu 20.04.4 LTS
Java version: 1.8.0_321
Python3 version: 3.8.10
Python3 Path: /usr/bin/python3
Env:
CC=gcc
CXX=g++
ELEMENTS=/root/ocssw/var/seawifs
EOS_LIB_PREFIX=linux64
FC=gfortran
GCC_TUNE=
HDFEOS_LIB=/root/ocssw/opt/EOS/lib/linux64
HRPT_STATION_IDENTIFICATION_FILE=/root/ocssw/share/seawifs/station/station_id.dat
L2GEN_ANC=/root/ocssw/var/anc
LIB3_BIN=/root/ocssw/opt/bin
LIB3_CHECK=0
LIB3_DIR=/root/ocssw/opt
LIB3_INC=/root/ocssw/opt/include
LIB3_LIB=/root/ocssw/opt/lib
NAVCTL=/root/ocssw/share/seawifs/nav
NAVQC=/root/ocssw/share/seawifs/nav
OCSSW_ARCH=linux_64
OCSSW_BIN=/root/ocssw/bin
OCSSW_DEBUG=0
OCSSW_MODIS=1
OCTS_REGISTRATION_TABLES=/root/ocssw/share/octs/nav
OCVARROOT=/root/ocssw/var
ORBCTL=/root/ocssw/share/seawifs/nav
PGSINC=/root/ocssw/opt/EOS/include
PGSLIB=/root/ocssw/opt/EOS/lib/linux64
PROJ_DATA=/root/ocssw/opt/share/proj
PROJ_LIB=/root/ocssw/opt/share/proj
SWFTBL=/root/ocssw/share/seawifs/qc
SWTBL=/root/ocssw/share/seawifs

I know this may not affect homework for the class, but it seems like a very useful software so I would like to get it operating if possible. If Docker is the problem, I may just try to install a different way.

Thanks!
Amy

aurisharahman
Posts: 6
Joined: Thu May 30, 2024 3:38 pm America/New_York
Answers: 0

Re: SEADAS errors for Windows/Docker

by aurisharahman » Thu May 30, 2024 3:41 pm America/New_York

Hello,

I'm working on the SeaDAS-OCSSW Client Server Configuration for Windows with the Docker method and for Step 4 I'm confused on where to download seadas.properties file from because it's not provided anywhere in the instructions.
https://seadas.gsfc.nasa.gov/client_server/#seadas-cc

Thank you,
Aurisha Rahman

Post Reply