cancel
Showing results for 
Search instead for 
Did you mean: 

DAA not starting - smdsetup.sh

Private_Member_19084
Active Contributor
0 Kudos

Hi experts,

since a few days the DAA of one system is not anylonger starting.

I checked today and did also see that smdsetup.sh of  /usr/sap/DAA/SMDA97/script directory is empty now.

I did a restore of that file and did execute the connection to solman again, however after making a restart of DAA the file is again empty and daa not starting.

Where can I find a helpful log of the DAA agent?

(we did also a host restart without success)

Kind regards

Accepted Solutions (1)

Accepted Solutions (1)

Private_Member_19084
Active Contributor
0 Kudos

So...really, very very strange.

File was switching to 0 bytes and also changing authorities.

After looking a bit I found out the reason LOL

It was a filled storage /usr/sap

I've extended it and restartet the host and after that it was working fine.

So please don't ask what was going on, but if you have the same problem maybe having a look on the FS

Kind regards

Answers (3)

Answers (3)

manumohandas82
Active Contributor
0 Kudos

check the crontabs of  user root ,sapadm  , <sid>adm

Something from OS only could delete / Make modifications to  those files anyways

Thanks ,

Manu

former_member182657
Active Contributor
0 Kudos

Hi,

DAA the file is again empty and daa not starting

Could you share results for command crontab -l with top from the OS .

Thanks,

Private_Member_19084
Active Contributor
0 Kudos

I get "no crontab for daaadm".

Should I try with another user?

manumohandas82
Active Contributor
0 Kudos

Hi Christian ,

You will find the logs under

/usr/sap/DAA/SMDA97/work


Is there any cron jobs running which deletes files from these folders ?



Thanks ,

Manu

Private_Member_19084
Active Contributor
0 Kudos

Hello Manu,

no, there is no job which is deleting files.

I mean the file is still there, it is just empty.

Which log file can I check there?
I've already checked "available", which is not including a helpful information.

And also sapstart.log, but also not really an error there.