View Full Version : [VU+ Duo] Sorry feeds are down for maintenance, please try again later!!
Hi Guys,
Two weeks ago i tried to update my box and got "Sorry feeds are down for maintenance, please try again later" message.
When i tried to update plugins i got "Sorry feeds are down for maintenace"
I tried for a few days to get it to work and ended up having to do a new install with the latest image.
I then installed ondamand through "download plugins" which worked and the online update worked too.
Now i have the same issues as before. I cant update the box or download any plugins.
Is there any way to fix this or would i have to do another new install?
Thank you for any help.
:thumbsup:
you probably just happened to timed your updates when vix did theirs.
nothing to worry about, i don't think.
The feeds have been set to unstable as the new image with the EPG and recording changes has been pushed to the server and set to unstable.
Hi, i have been trying for several days now at various times and i have set my settings to allow unstable updates but the issue is the same
The feeds have been set to unstable as the new image with the EPG and recording changes has been pushed to the server and set to unstable.
Prior to last night the feeds were stable. You could try a online update.
Sent from my GT-I9300 using Tapatalk 2
I have had this issue for over 2 weeks now. The only way i got around it was to re flash the box again and when i did it all was working as it should for a couple of days then the same issue arrises.
Prior to last night the feeds were stable. You could try a online update.
Sent from my GT-I9300 using Tapatalk 2
This problem keeps recurring for me also. re flash with Build 632 . I had to re flash the image previously because of this problem...But its cropped up again :eek: Not too sure if there are any further build updates from 632 ? but it wont even let me Download any plugins and receiving the same error about the servers . :confused: I have the software tab ...set too.... allow unstable updates , so this is not the problem.
Regards
polosolo
I ended doing another re flash with 632 and then updating to 642. Hopefuly this will be ok now. I will do an update if it goes again.
:thumbsup:
I ended doing another re flash with 632 and then updating to 642. Hopefuly this will be ok now. I will do an update if it goes again.
:thumbsup:
i had to do the same
This is for me a recurring issue on two of my 3 DUOs.
After few (variable) days of use the wget get corrupted and there's no way to di online update. Neither using telent commands. This Issue affects plugin downloads.
Not affecting network activities like sharing.
I have this same Issue again and it is becoming a real pain .I really wish the problem could be fix.
I had to reflash my last image because of this problem ,as it would not update or download plugins ...Same annoying message :mad:
Software downloads set to allow unstable in settings .will not software update via telnet , will not work with any image backups .
I did a full flash openvix-3.0.643-vuultimo_usb and then updated to 645 nps but now after a few days I get this same crappy message.
Same results as previous , so looks like I will have to reflash again. :eek: I really like the Vix image ,but this is a pain.
This needs pinpointing and sorting out by the Gurus Please.
Regards
polosolo
Mandanddeb
11-04-13, 18:07
Iv just tested my feeds and there accessible I know it's no fix but at least you know it's not everyone
why don't you set your
Menu>setup>system>software update= allow unstable (untested) updates to YES
Thanks for your input m8 but if you read my post carefully ...you will see this is not the issue. ;)
i had the same for weeks and weeks, the only resolution was to reflash again and again.... however a fresh usb flash of vix-649 via USB seemed to do the trick for me:thumbsup:
i had the same for weeks and weeks, the only resolution was to reflash again and again.... however a fresh usb flash of vix-649 via USB seemed to do the trick for me:thumbsup:
I thought the same on build 643 and updated to 645 build nps but after a few days ,,I got the dreaded message again :eek:
I have now reflashed with usb build 649 .. so Really hope that the gremlins have gone from this build.
Regards
polosolo
Starred Wolf Nu
18-04-13, 13:59
This is for me a recurring issue on two of my 3 DUOs.
After few (variable) days of use the wget get corrupted and there's no way to di online update. Neither using telent commands. This Issue affects plugin downloads.
Not affecting network activities like sharing.
Same for me, this problem seems to have started around v600 or so - sorry can't be specific.
VIX Guru's - this wget issue appears to be affecting more and more people, please help :)
It happened to me again. now on build 649 so hopefully this is ok :)
I have just tested the plugins are available on 3.0.649
Then I deactivated the network and tested again,and got the "down for maintainance" message
then restarted the network and tested again and they were available once more
Have you tested your network whenever that message appeared?
Rob van der Does
21-04-13, 13:56
I don't think this can be cured from the ViX-side: it looks like a local network issue.
I had this once, with one of my routers: I was unable to find any cause. Once the router had been replaced, I never got this problem again.
I don't think this can be cured from the ViX-side: it looks like a local network issue.
I had this once, with one of my routers: I was unable to find any cause. Once the router had been replaced, I never got this problem again.
Rob the issue is related to WGET that does not work. Maybe getting corrupted. I've pointed this many times.
For my tests it has nothing to do with router. It seems like somethig always get corrupted on 2 of my 3 duos.
Rob van der Does
21-04-13, 17:19
On next build de WGET time-out will be increased. Maybe that helps.
On next build de WGET time-out will be increased. Maybe that helps.
this should in som way fix the wget 255 error?
this should in som way fix the wget 255 error?
Hopefully yes but it will need testing by users suffering these problems as not every one does.
Sent from my GT-I9300 using Tapatalk 2
Hopefully yes but it will need testing by users suffering these problems as not every one does.
Sent from my GT-I9300 using Tapatalk 2
I'm here with Two Affected DUOs to test
Anyhow when can we expect this fix to be released?
Soon but cant say when as andy has had some problems with the image build machine.
Sent from my GT-I9300 using Tapatalk 2
I have been on build 649 clean flash and formatted HD for a week or so and not had a problem since :) This has been the longest run it`s been on without this error , from the 600 builds. Maybe formatting the HD helped ? as I never done this previously .
Glad to see the Dev`s addressing this annoying issue. :thumbsup:
Regards
polosolo
I have been on build 649 clean flash and formatted HD for a week or so and not had a problem since :) This has been the longest run it`s been on without this error , from the 600 builds. Maybe formatting the HD helped ? as I never done this previously .
Glad to see the Dev`s addressing this annoying issue. :thumbsup:
Regards
polosolo
I won't rely on that. I've encountered the prob after 10 days or so.
Even on Duo without Hdd.
Starred Wolf Nu
24-04-13, 11:08
Ok, have a look in your /usr/bin, you may find the wget has been renamed to -wget. Rename it back to wget and all should be back to normal :) I have no idea why/how this rename occurs though. Thanks Google you have saved me many a reflash :p
It does seem to go back to -wget every now and then though, just FTP back in and rename again. 10 second job. I'm happy with that until the devs manage to identify the issue.
Ok, have a look in your /usr/bin, you may find the wget has been renamed to -wget. Rename it back to wget and all should be back to normal :) I have no idea why/how this rename occurs though. Thanks Google you have saved me many a reflash :p
It does seem to go back to -wget every now and then though, just FTP back in and rename again. 10 second job. I'm happy with that until the devs manage to identify the issue.
This is a great discover!!!
Thx Starred Wolf Nu.
I've found that this is what has happend to me. Just renamed -wget to wget and now it's working.
Tomarrow I'll check on my father's on.
This is a great discovery.
I can confirm that on my father's DUO the wget was renamed to -wget too.
Fixed it's name and now it is fine.
So at this point the wget issue is not related to timeout... please let Andy know
Ok, have a look in your /usr/bin, you may find the wget has been renamed to -wget. Rename it back to wget and all should be back to normal :) I have no idea why/how this rename occurs though. .
Thank you Sir ..... Excellent news indeed. This is what I will now use if I see that dreaded (well not so dreaded now) message again.
I knew a Guru would come and save us . :D
Best Regards
sounds like some plugin that is installed messing with it. (like TSPanel messes with stuff)
sounds like some plugin that is installed messing with it. (like TSPanel messes with stuff)
Yo Andy, If you want here is the list of installed plugins on my two affected DUOS:
DUO A
CCcam 2.3.0 (vix)
A867 driver
cacheflush
DUO C
CCcam 2.3.0 (vix)
cacheflush
TechSat Keys Downloader V.1.4
**********************
DUO B has never been affected by this issue on any build (2.4 or 3.0) and I've installed on it much more plugins like
CCcam 2.3.0 (vix)
cacheflush
TechSat Keys Downloader V.1.4
OE-Alliance OnDemand Plugin
Mediaportal
**********************
Actually I missed some plugins in the above lists:
the correct list is the following:
DUO A (affected by wget issue)
CCcam 2.3.0 (vix)
A867 driver
cacheflush
OE-Alliance OnDemand Plugin
AspectRatioSwitch
SVDownloader
DUO C (affected by wget issue)
CCcam 2.3.0 (vix)
cacheflush
AspectRatioSwitch
TechSat Keys Downloader V.1.4
***************************************
DUO B (the one that has never had issues):
CCcam 2.3.0 (vix)
cacheflush
TechSat Keys Downloader V.1.4
OE-Alliance OnDemand Plugin
Mediaportal
AspectRatioSwitch
SVDownloader
RemoteChannelStreamConverter
WebMedia
***************************************
Actually I missed some plugins in the above lists:
the correct list is the following:
DUO A (affected by wget issue)
CCcam 2.3.0 (vix)
A867 driver
cacheflush
OE-Alliance OnDemand Plugin
AspectRatioSwitch
SVDownloader
DUO C (affected by wget issue)
CCcam 2.3.0 (vix)
cacheflush
AspectRatioSwitch
TechSat Keys Downloader V.1.4
***************************************
DUO B (the one that has never had issues):
CCcam 2.3.0 (vix)
cacheflush
TechSat Keys Downloader V.1.4
OE-Alliance OnDemand Plugin
Mediaportal
AspectRatioSwitch
SVDownloader
RemoteChannelStreamConverter
WebMedia
***************************************
if you can and have time, do fresh flash no restore, check that wget is ok, install one plugin at a time after each install plugin check for wget.
andy,
hi Andy,
what you suggest may be useless, and here is why.
In the past I've already done this test with no luck.
And I'll explain why:
I've done what you ask on Duo A. Just flashed and manually set all I needed. Then just Installed CCcam.
After about 7-10 days the receiver started to be affected by the issue.
FOr sure I can say that ALL of my DUOs some times crashes at night during crossEPG refresh.
Recently the DUO B was found freezed at the scheduled time for three consecutives days.
And about the crossEPG settings, all the three DUOs are set to grab SkyIT via OpenTV, and then Rai script and Mediaset script. That's all.
Anyway, I'll retry to check step-by-step as soon as I can (DUO-A is the main receiver of the home cccam serving the other two...)
Rob van der Does
27-04-13, 08:16
It's quite normal for a DUO not to be able to cope with Cross's EPG import. The way the plugin works, especially the parsing process, is very memory hungry. This can be overcome by using a SWAP-file.
I don't think there's any relation with the 'feeds down' problem.
It's quite normal for a DUO not to be able to cope with Cross's EPG import. The way the plugin works, especially the parsing process, is very memory hungry. This can be overcome by using a SWAP-file.
I don't think there's any relation with the 'feeds down' problem.
Rob, Was just going to be as much exhaustive as I can in describing my settings.
And yes I've set the largest available swap settings on all my three DUOs
Rob van der Does
27-04-13, 13:32
Rob, Was just going to be as much exhaustive as I can in describing my settings.
Yep, understood and appreciated.
And yes I've set the largest available swap settings on all my three DUOs
And still a crash during Cross-EPG? Maybe minimize the import, delete epg.dat (only after stopping E2), or use an even larger swap?
And still a crash during Cross-EPG? Maybe minimize the import, delete epg.dat (only after stopping E2), or use an even larger swap?
Actually DUO B has crashed for 3 days in a row. And than stopped to crash.
The swap file is the larger that I can choose.
Anyway since renaming -wget to wget I succesfully upgraded to latest build two days ago. So let's see what will eventually happen.
Oh damn!! Today after just 2 days after the fix via ftp DUO A showed again the "feed are down..." message.
And you know what?
I Used FTP to check /usr/bin and there's no trace of wget at all!!! Yes neither -wget is there.
This is the content of /usr/bin
[
[[
alsamixer
ar
awk
basename
bdpoll
bunzip2
bzcat
chage
cheetah
cheetah-analyze
cheetah-compile
chfn
chfn.shadow
chrt
chsh
chsh.shadow
chvt
clear
cmp
crontab
cut
dbclient
dbus-cleanup-sockets
dbus-daemon
dbus-monitor
dbus-send
dbus-uuidgen
dc
deallocvt
diff
dirname
dlist_test
dos2unix
du
eject
enigma2
enigma2.sh
env
ether-wake
event_rpcgen.py
expiry
expr
faillog
fgconsole
find
flock
free
fuser
get_device
get_driver
get_module
gpasswd
grab
groups
groups.shadow
gst-feedback
gst-feedback-0.10
gst-inspect
gst-inspect-0.10
gst-launch
gst-launch-0.10
gst-typefind
gst-typefind-0.10
gst-xmlinspect
gst-xmlinspect-0.10
gst-xmllaunch
gst-xmllaunch-0.10
head
hotplug_e2_helper
id
kbd_mode
killall
last
last.sysvinit
lastb
lastlog
less
logger
logname
lspci
lsusb
manhole
md5sum
mesg
mesg.sysvinit
mkfifo
nc
newgrp
newgrp.shadow
nmap
nmeter
nohup
nslookup
ntpdate
od
openssl
openvt
opkg
opkg-cl
opkg-key
passwd
passwd.shadow
patch
pcap-config
pgrep
pilconvert.py
pildriver.py
pilfile.py
pilfont.py
pilprint.py
printf
pyhtmlizer
python
python-config
python2.7
python2.7-config
readlink
realpath
renice
reset
run-parts
scp
sdparm
seq
setkeycodes
setsid
sg
sha1sum
sha256sum
sha512sum
showiframe
showkey
smemcap
sort
ssh
strings
su
systool
tail
tap2deb
tap2rpm
tapconvert
taskset
tee
telnet
test
time
timeout
top
tr
traceroute
traceroute6
trial
tty
turnoff_power
twistd
uniq
unix2dos
unxz
unzip
update-alternatives
uptime
users
utmpdump
volname
wall
wall.sysvinit
watch
wc
wg
which
who
whoami
whois
wpa_passphrase
xargs
xml2-config
xmlcatalog
xmllint
xzcat
yes
as you can notice now wget is renamed to wg (between wc and which)
Oh damn!! Today after just 2 days after the fix via ftp DUO A showed again the "feed are down..." message.
And you know what?
I Used FTP to check /usr/bin and there's no trace of wget at all!!! Yes neither -wget is there.
This is the content of /usr/bin
[
[[
alsamixer
ar
awk
basename
bdpoll
bunzip2
bzcat
chage
cheetah
cheetah-analyze
cheetah-compile
chfn
chfn.shadow
chrt
chsh
chsh.shadow
chvt
clear
cmp
crontab
cut
dbclient
dbus-cleanup-sockets
dbus-daemon
dbus-monitor
dbus-send
dbus-uuidgen
dc
deallocvt
diff
dirname
dlist_test
dos2unix
du
eject
enigma2
enigma2.sh
env
ether-wake
event_rpcgen.py
expiry
expr
faillog
fgconsole
find
flock
free
fuser
get_device
get_driver
get_module
gpasswd
grab
groups
groups.shadow
gst-feedback
gst-feedback-0.10
gst-inspect
gst-inspect-0.10
gst-launch
gst-launch-0.10
gst-typefind
gst-typefind-0.10
gst-xmlinspect
gst-xmlinspect-0.10
gst-xmllaunch
gst-xmllaunch-0.10
head
hotplug_e2_helper
id
kbd_mode
killall
last
last.sysvinit
lastb
lastlog
less
logger
logname
lspci
lsusb
manhole
md5sum
mesg
mesg.sysvinit
mkfifo
nc
newgrp
newgrp.shadow
nmap
nmeter
nohup
nslookup
ntpdate
od
openssl
openvt
opkg
opkg-cl
opkg-key
passwd
passwd.shadow
patch
pcap-config
pgrep
pilconvert.py
pildriver.py
pilfile.py
pilfont.py
pilprint.py
printf
pyhtmlizer
python
python-config
python2.7
python2.7-config
readlink
realpath
renice
reset
run-parts
scp
sdparm
seq
setkeycodes
setsid
sg
sha1sum
sha256sum
sha512sum
showiframe
showkey
smemcap
sort
ssh
strings
su
systool
tail
tap2deb
tap2rpm
tapconvert
taskset
tee
telnet
test
time
timeout
top
tr
traceroute
traceroute6
trial
tty
turnoff_power
twistd
uniq
unix2dos
unxz
unzip
update-alternatives
uptime
users
utmpdump
volname
wall
wall.sysvinit
watch
wc
wg
which
who
whoami
whois
wpa_passphrase
xargs
xml2-config
xmlcatalog
xmllint
xzcat
yes
as you can notice now wget is renamed to wg (between wc and which)
ok then something is messing with system files.
hi andy
some more feedback:
1- once again tried to rename wg back to wget.
At that point since a new update is on air I tried to perform the onair update via config menu, but got the error that a system process was ongoing...
2-This morning before starting from scratch by reflashing I wanted to try via Telnet to perform the update but the receiver refused me the access with this message:
Connection closed by foreign host.
*************** SESSION CLOSED **************
3- before flashing I went back to receiver to write down the error message reported at the above point 1. You know what, the receiver is updating itself without errors...
Rob van der Does
29-04-13, 17:18
Have a look at
http://vierko.org/tech/lightaidra-0x2012/
Have a look at
http://vierko.org/tech/lightaidra-0x2012/
Very interesting read rob, just goes to show why people should always enable authentication protocols on any Internet connected device and especially not to use default passwords or login details.
Sent from my iPad using Tapatalk HD
Have a look at
http://vierko.org/tech/lightaidra-0x2012/
Ok, and this should be interesting for DUO issue?
I mean, how should I check if my device is infected?
Assuming that I'm infected, I'm wondering why only 1 DUO is actually affected.
Second thing I'm using an Adsl router, all the devices in the LAN (computers and STBs) have static IPs.
The port for FTP, telent and web access are customized. Isn't this enough?
Rob van der Does
29-04-13, 19:41
Ok, and this should be interesting for DUO issue?
Well, have you heard of any other 'thing' that renames WGET?
Well, have you heard of any other 'thing' that renames WGET?
Sorry, I sent my message before completing it and It seems that You read my post before I edited it.
Robs, thank to your discovery I checked thoroughly my router forwarding rules and discovered that had one duplicated rule forwarding the plain 23 port to the wget affected DUO.
Fixed it.
Now. (forgive my poor linux knowledge in advance, I may be writing bullshit now on...) Since I'm only able to ftp and telent is refused, is there a way to access the "configuration" where the telnet password is stored and edit that file?
****************
I've to admit that I'm guilty since till this discovery I never thought about customizing telnet password. And so I'm wondering: if I customize that once performing a restore of the backed up setting the custom telnet password will be retained?
****************
Robs, thank to your discovery I checked thoroughly my router forwarding rules and discovered that had one duplicated rule forwarding the plain 23 port to the wget affected DUO.
Fixed it.
Now. (forgive my poor linux knowledge in advance, I may be writing bullshit now on...) Since I'm only able to ftp and telent is refused, is there a way to access the "configuration" where the telnet password is stored and edit that file?
****************
I've to admit that I'm guilty since till this discovery I never thought about customizing telnet password. And so I'm wondering: if I customize that once performing a restore of the backed up setting the custom telnet password will be retained?
****************
yes, login to telnet and type.
passwd root
and type in your new password, this wil be for both FTP and Telnet.
yes, login to telnet and type.
passwd root
and type in your new password, this wil be for both FTP and Telnet.
Actually, if your read back my post I was asking something else. Anyway never mind about that.
********************
I'd like to inform you that yesterday night I've reflashed the DUO-A (wget affected) and fixed all the firewall rules to block port 23 forwarding to it. I've customized the root password. And now on I'll let you know how it'll behave.
Ok, have a look in your /usr/bin, you may find the wget has been renamed to -wget. Rename it back to wget and all should be back to normal :) I have no idea why/how this rename occurs though. Thanks Google you have saved me many a reflash :p
It does seem to go back to -wget every now and then though, just FTP back in and rename again. 10 second job. I'm happy with that until the devs manage to identify the issue.
Great Find Star Wolf!!! :thumbsup:
I have been having the ''Sorry feeds are down for maintenance, please try again later'' issue crop up regularly and always resorted to a USB flash to update.
Thanks to your bit of advice, I find my own wget file is renamed at random intervals to ~wget...
a quick rename of the file and online update works a treat!
Thanks again!
Great Find Star Wolf!!! :thumbsup:
I have been having the ''Sorry feeds are down for maintenance, please try again later'' issue crop up regularly and always resorted to a USB flash to update.
Thanks to your bit of advice, I find my own wget file is renamed at random intervals to ~wget...
a quick rename of the file and online update works a treat!
Thanks again!
I'd be thanking Rob (http://www.world-of-satellite.com/showthread.php?27477-Sorry-feeds-are-down-for-maintenance-please-try-again-later!!&p=210902&viewfull=1#post210902) & getting your network in order rather than renaming a binary...
Great Find Star Wolf!!! :thumbsup:
I have been having the ''Sorry feeds are down for maintenance, please try again later'' issue crop up regularly and always resorted to a USB flash to update.
Thanks to your bit of advice, I find my own wget file is renamed at random intervals to ~wget...
a quick rename of the file and online update works a treat!
Thanks again!
Did you read post 44 in this thread ??.
http://www.world-of-satellite.com/showthread.php?27477-Sorry-feeds-are-down-for-maintenance-please-try-again-later!!&p=210902&viewfull=1#post210902
I'd be thanking Rob (http://www.world-of-satellite.com/showthread.php?27477-Sorry-feeds-are-down-for-maintenance-please-try-again-later!!&p=210902&viewfull=1#post210902) & getting your network in order rather than renaming a binary...
Did you read post 44 in this thread ??.
http://www.world-of-satellite.com/showthread.php?27477-Sorry-feeds-are-down-for-maintenance-please-try-again-later!!&p=210902&viewfull=1#post210902
From reading the post Rob linked and checking out the suggested binary/files along with having fairly good firewall settings,(I hope....Nothing connected is ever 100% secure of course) prior to renaming the binary in question and still having the issue randomly crop up even after reflashing, I used Starred wolfs suggestion and it allowed me an online update.
But I will go through my network settings/firewall and also recheck \var and \etc for any of the obvious anamolies
Rob van der Does
01-05-13, 00:33
From reading the post Rob linked and checking out the suggested binary/files along with having fairly good firewall settings,(I hope....Nothing connected is ever 100% secure of course) prior to renaming the binary in question and still having the issue randomly crop up even after reflashing, I used Starred wolfs suggestion and it allowed me an online update.
But I will go through my network settings/firewall and also recheck \var and \etc for any of the obvious anamolies
Pretty sure that if your box still suffers from the 'wget-renaming-'issue you have an 'aidra' infected device in your network.
Be aware it is aimed at devices running embedded Linux, so most routers and many STB's will be a target.
Or can you think of any other reason for your files to be spontaneous renamed?
Starred Wolf Nu
02-05-13, 16:05
So to be clear if I reboot my Duo it will remove any evidence of Aidra from that machine?
In my case I'm guessing my router is the issue though (running DD-WRT). Would my router being infected cause issues on my Duo?
Rob van der Does
02-05-13, 17:52
So to be clear if I reboot my Duo it will remove any evidence of Aidra from that machine?
If you reflash I would say yes, because the flash will be completely erased.
Only worry might be a connected storage device.
In my case I'm guessing my router is the issue though (running DD-WRT). Would my router being infected cause issues on my Duo?
I presume so, but I'm far from an expert in this area. Anyway: make sure not to forward any port and to personalise the routers password.
Starred Wolf Nu
02-05-13, 21:04
OK reset router to default and set new password. Also reflashed duo and set new root password and telnet is now working. Will see how my wget issue goes...
Sent from my MID using Tapatalk HD
Rob van der Does
03-05-13, 03:33
OK reset router to default .....
IF the router would be affected (and again: no idea if it really is) I would say it has to be reflashed as well.
But now I would await the results of your present setup.
Good luck!
At my father's home the router has no option to customize external ports. I mean both external and internal ports have to be the same.
Is it possible to customize on DUO itself FTP and TELNET ports?
Starred Wolf Nu
05-05-13, 20:57
IF the router would be affected (and again: no idea if it really is) I would say it has to be reflashed as well.
But now I would await the results of your present setup.
Good luck!
So far so good. I'm guessing my router was to blame as I'd previously reflashed the duo many times without success.
Sent from my GT-I9100 using Tapatalk 2
Renaming -wget to wget did the trick for me many thanks for this great find.
Renaming -wget to wget did the trick for me many thanks for this great find.
if you had to rename the wget file then your receiver and router etc are infected with a virus.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.