Opened 19 years ago
Closed 19 years ago
#2875 closed defect (fixed)
mythweb does not use storagegroup streaming does not work
| Reported by: | Owned by: | xris | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythweb | Version: | head |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Up to [12424] streaming does not work in mythweb.
I only get an error message 'xxx does not exist in the recordings directory.'.
After some search I realized that mythweb is not able to use storagegroup by now.
Change History (6)
comment:1 by , 19 years ago
follow-up: 3 comment:2 by , 19 years ago
It's on same backend.
In modules/stream/handler.pl existence of $filename/$basename is checked (line 73 ff.).
comment:3 by , 19 years ago
I just created following 'workaround'
line 72 ff.: <code># Get the filename on disk
$sh = $dbh->prepare('SELECT dirname
FROM storagegroup
WHERE hostname=?');
$sh->execute(hostname);
print header();
my $file; while ( ($filename) = $sh->fetchrow_array() ) {
if ( -e "$filename/$basename" ) {
$file = "$filename/$basename"; last;
}
} $sh->finish;
$filename = $file;</code>
this seams to work with both of my storagegroups but still needs much work to respect stored storagegroups in recorded.
comment:4 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
(In [12429]) update the perl stream handler.pl file to use storage group directories instead of RecordFilePrefix. closes #2875
comment:5 by , 19 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Your fix assumes that there is only ONE possible dirname per storagegroup.
In reality there can be more than one dirnames per storagegroup. e. g.:
mysql> select * from storagegroup; +----+-----------+----------+--------------+ | id | groupname | hostname | dirname | +----+-----------+----------+--------------+ | 1 | Default | neptun | /mnt/store/ | | 2 | Default | neptun | /mnt/store1/ | +----+-----------+----------+--------------+ 2 rows in set (0.00 sec)
So there may be more than just one result to check.

Are the recordings on the local drive or on a different backend?