Open crose-project opened 2 years ago
muratugureminoglu
commented
2 years ago @crose-project I understand your situation, but adding this to the installation script may give incorrect information. However, let's consider this among ourselves.
A kindly suggestion is that, you can mount /usr/local/antmedia directory to a large-space disk configured with LVM or use a service like S3. After all, Ant Media Server is around 335Mb.
crose-project
commented
2 years ago Dear @muratugureminoglu, thanks for your response. The problem for us was a broken AMS installation after we tried an AMS update. And our motiviation to open this feature request was to help/protect others to do the same error.
For us, 'incorrect information' would have been more appreciated than a broken AMS installation ;-)
Nevertheless, thanks for your support and your great streaming server.
muratugureminoglu
commented
2 years ago @crose-project Thanks for your feedback. We will consider it.
Regards.
muratugureminoglu
commented
2 years ago Hi @crose-project
Which directory are you connecting to with a symbolic link? Actually, when I take a look at the install script, if you connect the streams directory as a symlink, you will not have any problems with the restore operations[1]. We will also do a work for disk space calculation in the next release.
[1] https://github.com/ant-media/Scripts/blob/master/install_ant-media-server.sh#L54#L56
Dear AMS
We had a lot of recordings in the webapps directory and the webapps directory (not the individually streams directories) is a symlink to an extra storage drive. The installer creates a backup and after installation it restores all user data from the backup to new /usr/local/antmedia directory - unfortunately the new directory /usr/local was on our root disk with only 0.5TB. The recordings have been 3.5TB - and so the installer filled the root disk completely and crashed at the end (disk full). Maybe you can do a disk free check before starting the whole upgrade?
Thanks Carsten