I've now tried several times to install the upgrade on my B2, but the led just keeps blinking at 2hz. Also the USB only shows the led having power and no activity.
I formatted the usb for fat32 and copied the install folder to the root.
Is there anything I missed, why it is not installing?
Please note the new address for this forum : forum.excito.org. The old address redirects here but I don't know for how long. Thanks !
New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !
Search found 16 matches
- 16 Apr 2012, 10:38
- Forum: Software releases
- Topic: Release notes for Excito Bubba 2 software version 2.4.1
- Replies: 25
- Views: 92917
- 17 Jun 2011, 14:03
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
No, I wasn't using the mail system. I had webmin installed and using virtualmin. The latter used a cronjob to send messages which ended up in the maildrop. Since I'm not using webmin anymore, I completely uninstalled everything related to that and removed the cronjob.
So now everything is running ...
So now everything is running ...
- 17 Jun 2011, 13:32
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
Thanks for all the help Eek. I cleared the maildrop using Now I have 85% free space again.
Do I really need the maildrop? Or is there a way to regulate the files created?
Code: Select all
postsuper -d ALL -v
Do I really need the maildrop? Or is there a way to regulate the files created?
- 17 Jun 2011, 11:13
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
Thanks for the info. The sorted by filesize also returns files on my storage volumes, while I think I need to clear space on the system volume (but not really sure). Looking at the result of the filesystem:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 9621848 9421452 0 100 ...
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 9621848 9421452 0 100 ...
- 17 Jun 2011, 10:54
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
That give's me the following:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 9621848 9421452 0 100% /
tmpfs 127900 0 127900 0% /lib/init/rw
udev 10240 24 10216 1% /dev
tmpfs 127900 4 127896 1% /dev/shm
/dev/mapper/bubba-storage
950669364 42960328 859417812 5% /home
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 9621848 9421452 0 100% /
tmpfs 127900 0 127900 0% /lib/init/rw
udev 10240 24 10216 1% /dev
tmpfs 127900 4 127896 1% /dev/shm
/dev/mapper/bubba-storage
950669364 42960328 859417812 5% /home
- 17 Jun 2011, 10:44
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
I found some lines:
Jun 17 16:16:45 bubba avahi-daemon[21603]: Found user 'avahi' (UID 109) and group 'avahi' (GID 111).
Jun 17 16:16:45 bubba avahi-daemon[21603]: Successfully dropped root privileges.
Jun 17 16:16:45 bubba avahi-daemon[21603]: write(): No space left on device
Jun 17 16:16:45 ...
Jun 17 16:16:45 bubba avahi-daemon[21603]: Found user 'avahi' (UID 109) and group 'avahi' (GID 111).
Jun 17 16:16:45 bubba avahi-daemon[21603]: Successfully dropped root privileges.
Jun 17 16:16:45 bubba avahi-daemon[21603]: write(): No space left on device
Jun 17 16:16:45 ...
- 17 Jun 2011, 10:28
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
Hi Eek,
Thanks for the suggestion. I tried restarting the avahi-deamon, but it fails. Where to go from here?
Thanks for the suggestion. I tried restarting the avahi-deamon, but it fails. Where to go from here?
- 17 Jun 2011, 08:51
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
Re: bubba.local not resolved
Thanks Daniel, although I'm not sure what to look for in the log. I also restarted the samba before, with no result. But when now using the afp to connect to a share, the smb seems to work again also.
Besides that, the http://bubba.local still doesn't resolve. But that ofcourse has nothing to do ...
Besides that, the http://bubba.local still doesn't resolve. But that ofcourse has nothing to do ...
- 17 Jun 2011, 07:04
- Forum: B2 & B3 Support
- Topic: bubba.local not resolved
- Replies: 16
- Views: 21570
bubba.local not resolved
Hi,
I've been using my B2 for two years now and it is still working fine. However, since last week, the http://bubba.local doesn't resolve anymore so I have to use the ip-address. Also on my MacBook I cannot access the smb mount anymore.
Any ideas on how to solve this?
Thanks in advance,
Marco
I've been using my B2 for two years now and it is still working fine. However, since last week, the http://bubba.local doesn't resolve anymore so I have to use the ip-address. Also on my MacBook I cannot access the smb mount anymore.
Any ideas on how to solve this?
Thanks in advance,
Marco
- 16 Apr 2010, 11:09
- Forum: Bubba Server Support
- Topic: Xbox360 streaming
- Replies: 0
- Views: 4880
Xbox360 streaming
Since I just got my Bubba and the last post about this is about a year old, Is there already a good solution of streaming audio and video from the Bubba|Two to the Xbox360? And since I'm a linux noob, if there is a solution how do I implement it?
- 16 Apr 2010, 08:08
- Forum: B2 & B3 Support
- Topic: Error after first update
- Replies: 9
- Views: 13159
Re: Error after first update
I can access the web-gui and the upgrade works fine now. And I can access it from a windows machine. So I might restart my Mac.
Thanks again.
Thanks again.
- 16 Apr 2010, 07:57
- Forum: B2 & B3 Support
- Topic: Error after first update
- Replies: 9
- Views: 13159
Re: Error after first update
Check! the hostname says bubba.
One more thing, bubba now show in Finder, but connection fails?
One more thing, bubba now show in Finder, but connection fails?
- 16 Apr 2010, 07:52
- Forum: B2 & B3 Support
- Topic: Error after first update
- Replies: 9
- Views: 13159
Re: Error after first update [SOLVED]
I added 127.0.0.1 bubba to the etc/hosts file. That seems to do the trick!
Thanks for your help!
Thanks for your help!
- 16 Apr 2010, 07:49
- Forum: B2 & B3 Support
- Topic: Error after first update
- Replies: 9
- Views: 13159
Re: Error after first update
I'm not really used to using the terminal and linux commando's, so bear with me...
This is in my hosts file:
127.0.0.1 localhost.localdomain localhost
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
And ...
This is in my hosts file:
127.0.0.1 localhost.localdomain localhost
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
And ...
- 16 Apr 2010, 07:24
- Forum: B2 & B3 Support
- Topic: Error after first update
- Replies: 9
- Views: 13159
Re: Error after first update
Hi Kiff,
Thanks for the reply, here's what I get from you dkpg line:
Setting up bubba-backend (1.9.16) ...
Creating new generic self-signed certificate: /etc/ssl/certs/dovecot.pem
(replace with hand-crafted or authorized one if needed).
hostname: Unknown host
dpkg: error processing bubba-backend ...
Thanks for the reply, here's what I get from you dkpg line:
Setting up bubba-backend (1.9.16) ...
Creating new generic self-signed certificate: /etc/ssl/certs/dovecot.pem
(replace with hand-crafted or authorized one if needed).
hostname: Unknown host
dpkg: error processing bubba-backend ...