[chanalku91]

Hey,

If you wanna play around with an LXC container, then this is for you: https://microlxc.net

Specs:
- 1x Core (Shared)
- 128, 256MB or 512MB
- 1.28, 2.56GB or 50GB
- 25Mbit Uplink @ 200GB or 5TB
- 20x forwarded Ports v4
- /64 or /70 Subnet v6

You can pick from multiple locations, depending if stock is available.

The Requirements to get one
- Existing account since 6 months, here on Post4VPS
- You need to have 100 posts before you apply
- Reputation needs to be at 5 Positive ratings or higher

Play nice! zero abuse tolerance.
TOR, I2P, Torrent, Mining, Port Scanning or any other ilegal stuff.
If we take notice, that a LXC gets abused, the LXC will be terminated.

How to get one
- Go to: https://microlxc.net/
- Place an Request
- After the Bot verified you, you get a Token, post that on here.
- Keep the Page open and follow the progress bar

Things you should know:
- The Service is provided with no SLA, but we try out best to keep everything running smoothly.
- Support will be provided over P4V PM or via email.
- No Backups are done on our side, You are responsible for taking backups of your data.
- There is no term guarantee

If you have any suggestions, lemme know.

Neoon

I rebuilt the VPS for basic script testing!

Please reply on this topic on Post4VPS,
with the following token:

f072-ed39-8d9c-0497

[Neoon]

NL has been rebooted for a network maintenance, SR-IOV has been enabled for better network performance.

[Neoon]

Another Maintenance announcement:

- NL will be moved into another rack on Tuesday, it will be de racked and racked up again so should not take long, no exact time window on that.
- LA, SG and NO have currently issues with the LVM backend, which results in poor I/O performance or failed deployments in SG.
The Plan would be for these locations, to migrate existing containers to a new LVM pool, which should solve these issues.
However, the operation could lead to data loss so I advise anyone if you have a container in one of these locations, take a backup before they will be migrated.

This will take place at the following days:

LA Friday, 16:00 GMT, approximately 1 hour
SG Friday 19:00 GMT, approximately 1 hour
NO Sunday, 19:00 GMT, approximately 2 hours

The Downtime will likely to be shorter for each container, as long nothing comes in-between.
During the maintenance, you won’t be able to control the container via microlxc.net 1.

After the maintenance stock will be available again on these locations, including NO.
Tokyo is not affected by this, however if we upgrade NL and AU, we likely will performance this maintenance additional or if it becomes necessary.

CH will be not moved to another LVM Backend, since I plan to discontinue it, due to the network related issues.
However don’t plan to discontinue CH until we have a replacement, currently I am still looking for one.
I keep you updated on this.

[tbelldesignco]

470d-4f2a-3cd7-ad15

I am so excited to test this out! Thank you for this opportunity!

[Neoon]

SG and LA migrations are done, total downtime about 3 minutes + 1 minute for each container. LA took a bit longer because Virtualizor messed it up again and broke v6.

Next & last migration for now is NO on the weekend.

[tiwil]

Hello there,

I want to grab a new one in Singapore. This one is for my new project that collects data and save it as a dataset that would be uploaded to Github and Kaggle daily.

Here is my token: 68d5-6e38-0e29-acb4

Cheers!

Edit:
Question: Can we install Python 3.8 inside? I cannot install. It always returns error. I believe this is CPU related error since it's very limited.

[Neoon]

Hello there,

I want to grab a new one in Singapore. This one is for my new project that collects data and save it as a dataset that would be uploaded to Github and Kaggle daily.

Here is my token: 68d5-6e38-0e29-acb4

Cheers!

Edit:
Question: Can we install Python 3.8 inside? I cannot install. It always returns error. I believe this is CPU related error since it's very limited.

Yes, error message? Otherwise I can't help you.
I see no point why it should be not possible.

[tiwil]

Below is the error

Code: (Select All)

gcc: internal compiler error: Killed (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
Makefile:1708: recipe for target 'Objects/unicodeobject.o' failed
make[3]: *** [Objects/unicodeobject.o] Error 4
make[3]: Leaving directory '/root/Python-3.8.7'
Makefile:507: recipe for target 'build_all_generate_profile' failed
make[2]: *** [build_all_generate_profile] Error 2
make[2]: Leaving directory '/root/Python-3.8.7'
Makefile:481: recipe for target 'profile-gen-stamp' failed
make[1]: *** [profile-gen-stamp] Error 2
make[1]: Leaving directory '/root/Python-3.8.7'
Makefile:492: recipe for target 'profile-run-stamp' failed
make: *** [profile-run-stamp] Error 2

When searching for this, I found this thread at Stackoverflow. It says most likely it's memory issue since the VPS is very limited in memory. I don't ran "make -j 8", I ran "make" only. It should automatically detect how many cores inside the VPS. I'm installing Python 3.8.7 anyway.

I still remember that I have used your VPS before and have Python 3 installed and running smoothly. I just forget how to install it again, haha!

Edit: I just found out that software-properties-common ships with Python 3.7 inside, which is fine for me to work with. I only need to install it and now I do have Python 3 inside my VPS. Apologies for any issue

[Neoon]

Below is the error

Code: (Select All)

gcc: internal compiler error: Killed (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-6/README.Bugs> for instructions.
Makefile:1708: recipe for target 'Objects/unicodeobject.o' failed
make[3]: *** [Objects/unicodeobject.o] Error 4
make[3]: Leaving directory '/root/Python-3.8.7'
Makefile:507: recipe for target 'build_all_generate_profile' failed
make[2]: *** [build_all_generate_profile] Error 2
make[2]: Leaving directory '/root/Python-3.8.7'
Makefile:481: recipe for target 'profile-gen-stamp' failed
make[1]: *** [profile-gen-stamp] Error 2
make[1]: Leaving directory '/root/Python-3.8.7'
Makefile:492: recipe for target 'profile-run-stamp' failed
make: *** [profile-run-stamp] Error 2

When searching for this, I found this thread at Stackoverflow. It says most likely it's memory issue since the VPS is very limited in memory. I don't ran "make -j 8", I ran "make" only. It should automatically detect how many cores inside the VPS. I'm installing Python 3.8.7 anyway.

I still remember that I have used your VPS before and have Python 3 installed and running smoothly. I just forget how to install it again, haha!

Edit: I just found out that software-properties-common ships with Python 3.7 inside, which is fine for me to work with. I only need to install it and now I do have Python 3 inside my VPS. Apologies for any issue

Compiling stuff on 256MB may likely not work, if the location does not matter, we got Norway with 512MB.
Otherwise, the project is focused on exotic locations, hence low memory.

And most recent distros are using 3.7 anyway, would be the way to go as you said.

[fChk]

@Neoon

My container exits every 2/3 days and I must login to start it again. Is it a memory issue ?..