search

ail-project / lacus

Lacus is a capturing system using playwright, as a web service.
BSD 3-Clause "New" or "Revised" License
43 stars 3 forks source link

Can't start Lacus Crawler #22

Closed Pranav-2301 closed 2 months ago

Pranav-2301 commented 2 months ago

Hello,

I am able to install the AIL framework on port 7000 and it runs perfect.

Environment Operating System: Ubuntu 20.04 Azure VM, with all the required inbound port rules set up. Python Version: 3.10 Poetry Version: 1.8.3

Moving ahead, I was trying to install the Lacus by following the installation steps mentioned in the git repository.

everything was fine until the step where I had to Initialize the config and install playwright browsers and run : poetry run update --init

Error Encountered

(lacus-py3.10) pg@Ubuntu:~/ail-framework/lacus$ poetry run update --init
No logging config file available.
Falling back on sample config, please initialize the logging config file.
* Update repository.

Already up to date.

* Install/update dependencies.
Installing dependencies from lock file

No dependencies to install or update

Installing the current project: lacus (1.10.0)

* Install or make sure the playwright browsers are installed.

* Validate configuration files.
The entries in /home/pg/ail-framework/lacus/config/generic.json are valid.

* Update configuration files.
No updates needed in /home/pg/ail-framework/lacus/config/generic.json.

* Restarting
Continue? (y/N) y
Restarting with poetry...
(lacus-py3.10) pg@Ubuntu:~/ail-framework/lacus$ No logging config file available.
Falling back on sample config, please initialize the logging config file.
2024-08-22 20:21:06,505 Website INFO:Initializing Website
2024-08-22 20:21:06,507 Website INFO:Launching Website
[2024-08-22 20:21:06 +0000] [16612] [INFO] Starting gunicorn 23.0.0
[2024-08-22 20:21:06 +0000] [16612] [INFO] Listening at: http://0.0.0.0:7100 (16612)
[2024-08-22 20:21:06 +0000] [16612] [INFO] Using worker: sync
[2024-08-22 20:21:06 +0000] [16613] [INFO] Booting worker with pid: 16613
[2024-08-22 20:21:06 +0000] [16614] [INFO] Booting worker with pid: 16614
No logging config file available.
Falling back on sample config, please initialize the logging config file.
2024-08-22 20:21:06,750 CaptureManager INFO:Initializing CaptureManager
2024-08-22 20:21:06,753 CaptureManager INFO:Launching CaptureManager
[2024-08-22 20:21:06 +0000] [16615] [INFO] Booting worker with pid: 16615
[2024-08-22 20:21:06 +0000] [16616] [INFO] Booting worker with pid: 16616
[2024-08-22 20:21:06 +0000] [16617] [INFO] Booting worker with pid: 16617
[2024-08-22 20:21:06 +0000] [16618] [INFO] Booting worker with pid: 16618
[2024-08-22 20:21:06 +0000] [16619] [INFO] Booting worker with pid: 16619
[2024-08-22 20:21:07 +0000] [16620] [INFO] Booting worker with pid: 16620
[2024-08-22 20:21:07 +0000] [16621] [INFO] Booting worker with pid: 16621
[2024-08-22 20:21:07 +0000] [16622] [INFO] Booting worker with pid: 16622
No logging config file available.
Falling back on sample config, please initialize the logging config file.

Can you please help me out with this issue ?

Rafiot commented 2 months ago

As far as I cal tell, it all started all fine. The message you get is simply because it falls back to the default logging config file.

Can you try to run a capture and see what happen?

Pranav-2301 commented 2 months ago

Bingo ! it ran. Thank you very much for replying promptly !

Rafiot commented 2 months ago

You're welcome!