Expand my Community achievements bar.

SOLVED

Error in AEMaaCS deployment

Avatar

Level 3

Hello

Has anyone experienced this following error on a cloud deploy in the deployment section of the pipeline and if yes, what can be done about it.

Thanks

Yonit

 

Fluent Bit v1.7.4
* Copyright (C) 2019-2021 The Fluent Bit Authors
* Copyright (C) 2015-2018 Treasure Data
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2022/04/01 01:31:24] [ info] [engine] started (pid=17)
[2022/04/01 01:31:24] [ info] [storage] created root path /var/log/flb-storage/
[2022/04/01 01:31:24] [ info] [storage] version=1.1.1, initializing...
[2022/04/01 01:31:24] [ info] [storage] root path '/var/log/flb-storage/'
[2022/04/01 01:31:24] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2022/04/01 01:31:24] [ info] [storage] backlog input plugin: storage_backlog.3
[2022/04/01 01:31:24] [error] [sqldb] cannot open database /var/log/aem/logs_error.db
[2022/04/01 01:31:24] [error] [input:tail:tail.1] could not open/create database
[2022/04/01 01:31:24] [ info] [input:storage_backlog:storage_backlog.3] queue memory limit: 95.4M
[2022/04/01 01:31:24] [ info] [http_server] listen iface=0.0.0.0 tcp_port=2020
[2022/04/01 01:31:24] [ info] [sp] stream processor started
[2022/04/01 01:31:24] [ info] [input:tail:tail.0] inotify_fs_add(): inode=45358773 watch_fd=1 name=/opt/aem/work/logs/job.log
pod/cm-p42306-e166537-aem-index-updates-h4bjf-vpx6m annotated

1 Accepted Solution

Avatar

Correct answer by
Community Advisor
3 Replies

Avatar

Correct answer by
Community Advisor

Hi,

Maybe you can try trailing build logs

https://www.opsinventor.com/tailing-and-viewing-adobe-cloud-manager-build-logs/



Arun Patidar

Avatar

Level 3

I'm confused here.  We can already see the log output.  How would seeing it as it's being deployed make a difference?

Avatar

Level 3

Hi.  I am going to give some actual insight into this for the sake of other people having a similar problem.  In the end this was due to a problem in content with the ancestors of a page not all being published, although I fail to see why this should have caused a failed deployment.