18.04 Server can log in remote but not localHow can I add items to Xfce root menu?LocalHost LoginUbuntu 18.04 Server - GUI remote accessremote desktop from windows10 to ubuntu without log out
Are there any real life instances of aircraft aborting a landing to avoid a vehicle?
How much transparency about runway should I expect from startup employer?
Features of a Coda section
On the finite simple groups with an irreducible complex representation of a given dimension
Why does Thorin tell Bilbo that he has "keen eyes"?
Did Bercow say he would have sent the EU extension-request letter himself, had Johnson not done so?
help solving for delta in epsilon delta proof
Continents with simplex noise
What does a single quote inside a C# date time format mean?
Is Dom based XSS still a valid security concern in modern browsers?
Hell0 W0rld! scored by ASCII values
Meaning of 'off one's brake fluid'
Wrapping tikz environment with savebox
Right way to say I disagree with the design but ok I will do
Can only rich people become president?
What are the applications of the Mean Value Theorem?
What would an asteroid impact feel like to someone standing on the moon?
I can be found near gentle green hills and stony mountains
Nobody can solve this puzzle
Non-differentiable Lipschitz functions
Dangers of being sympathetic to the killer
Are the Shimano derailleurs sold on Ali Express genuine or fake?
Multiple devices with one IPv6 to the Internet?
Why combine commands on a single line in a Bash script?
18.04 Server can log in remote but not local
How can I add items to Xfce root menu?LocalHost LoginUbuntu 18.04 Server - GUI remote accessremote desktop from windows10 to ubuntu without log out
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
After reading through the forums, I feel I have the opposite issue of most remote access issues.
I installed Ubuntu 18.04 Server and logged in. Installed Xfce desktop and Mozilla Firefox to allow me to look up additional information about configuring a Dual Wan (and bonded nic) setup. Everything worked fine. Set up a 3rd (as #2/#3 are bonded) NIC with the intention of using it as LAN only / remote in from my desktop.
Able to SSH in with putty, but noticed I've got some routing/NAT weirdness going on, as websites either load instantly / time out, same with sudo apt-get update, etc... Assuming they're going out/coming in on the different interfaces. Went back in to log in locally today on the server and it's saying "Failed to Execute Login Command", screen flashes something to quick to read and then refreshes the desktop.
As it had been a week since I'd been able to work the project, I thought 'Dummy, you must have put the password in wrong'. After several attempts, I came back to my desktop in the office and tried to SSH in with the same username/password and got right in!
So, I have access to continue to try and fix w/e weird routing/NAT/whatever issue I have through SSH, but cannot log in local now and have no idea why. Possibly some sort of Xfce Desktop issue? At this point I would even take shutting down the desktop log in locally without the GUI.
18.04 login xfce
add a comment
|
After reading through the forums, I feel I have the opposite issue of most remote access issues.
I installed Ubuntu 18.04 Server and logged in. Installed Xfce desktop and Mozilla Firefox to allow me to look up additional information about configuring a Dual Wan (and bonded nic) setup. Everything worked fine. Set up a 3rd (as #2/#3 are bonded) NIC with the intention of using it as LAN only / remote in from my desktop.
Able to SSH in with putty, but noticed I've got some routing/NAT weirdness going on, as websites either load instantly / time out, same with sudo apt-get update, etc... Assuming they're going out/coming in on the different interfaces. Went back in to log in locally today on the server and it's saying "Failed to Execute Login Command", screen flashes something to quick to read and then refreshes the desktop.
As it had been a week since I'd been able to work the project, I thought 'Dummy, you must have put the password in wrong'. After several attempts, I came back to my desktop in the office and tried to SSH in with the same username/password and got right in!
So, I have access to continue to try and fix w/e weird routing/NAT/whatever issue I have through SSH, but cannot log in local now and have no idea why. Possibly some sort of Xfce Desktop issue? At this point I would even take shutting down the desktop log in locally without the GUI.
18.04 login xfce
add a comment
|
After reading through the forums, I feel I have the opposite issue of most remote access issues.
I installed Ubuntu 18.04 Server and logged in. Installed Xfce desktop and Mozilla Firefox to allow me to look up additional information about configuring a Dual Wan (and bonded nic) setup. Everything worked fine. Set up a 3rd (as #2/#3 are bonded) NIC with the intention of using it as LAN only / remote in from my desktop.
Able to SSH in with putty, but noticed I've got some routing/NAT weirdness going on, as websites either load instantly / time out, same with sudo apt-get update, etc... Assuming they're going out/coming in on the different interfaces. Went back in to log in locally today on the server and it's saying "Failed to Execute Login Command", screen flashes something to quick to read and then refreshes the desktop.
As it had been a week since I'd been able to work the project, I thought 'Dummy, you must have put the password in wrong'. After several attempts, I came back to my desktop in the office and tried to SSH in with the same username/password and got right in!
So, I have access to continue to try and fix w/e weird routing/NAT/whatever issue I have through SSH, but cannot log in local now and have no idea why. Possibly some sort of Xfce Desktop issue? At this point I would even take shutting down the desktop log in locally without the GUI.
18.04 login xfce
After reading through the forums, I feel I have the opposite issue of most remote access issues.
I installed Ubuntu 18.04 Server and logged in. Installed Xfce desktop and Mozilla Firefox to allow me to look up additional information about configuring a Dual Wan (and bonded nic) setup. Everything worked fine. Set up a 3rd (as #2/#3 are bonded) NIC with the intention of using it as LAN only / remote in from my desktop.
Able to SSH in with putty, but noticed I've got some routing/NAT weirdness going on, as websites either load instantly / time out, same with sudo apt-get update, etc... Assuming they're going out/coming in on the different interfaces. Went back in to log in locally today on the server and it's saying "Failed to Execute Login Command", screen flashes something to quick to read and then refreshes the desktop.
As it had been a week since I'd been able to work the project, I thought 'Dummy, you must have put the password in wrong'. After several attempts, I came back to my desktop in the office and tried to SSH in with the same username/password and got right in!
So, I have access to continue to try and fix w/e weird routing/NAT/whatever issue I have through SSH, but cannot log in local now and have no idea why. Possibly some sort of Xfce Desktop issue? At this point I would even take shutting down the desktop log in locally without the GUI.
18.04 login xfce
18.04 login xfce
asked Jun 8 at 18:30
user99056user99056
311 silver badge4 bronze badges
311 silver badge4 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
So here is what I found out. As I was troubleshooting other issues that had shown up (prior to getting on to the routing/NAT issue, I found that I now had no way to even run sudo apt-get update, as I was getting all sorts of 'Failed to write, drive full' errors).
Long story short, apparently even though I have a 410G raid set up on the server and had partitioned it with LVM upon the original install, only 4GB was actually being used from the installer on root and I had the following:
System information as of Sat Jun 8 15:40:10 UTC 2019
=> / is using 95.7% of 3.87GB
After resizing the /dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.8G 0 100% / I thought I'd try to log in and Voila! I was able to log in again. Not sure if I missed something the night I did the install or what, as previously I had always done up specific partition sizes based off of what I'd read online (e.g. separate root / tmp / home / etc) but this time I went with what everyone recommended was let it do LVM and let it auto populate/adjust. It gave me the full 410GB on the LVM but stuck root at 4gb which had filled up, thus not letting me log in with the GUI (local) nor do any updates/etc.
Figured I would post the solution I found in case anyone else had issues with not being able to log in to the Desktop GUI and turns out it was a full root partition. Thanks all! ~AW
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1149644%2f18-04-server-can-log-in-remote-but-not-local%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So here is what I found out. As I was troubleshooting other issues that had shown up (prior to getting on to the routing/NAT issue, I found that I now had no way to even run sudo apt-get update, as I was getting all sorts of 'Failed to write, drive full' errors).
Long story short, apparently even though I have a 410G raid set up on the server and had partitioned it with LVM upon the original install, only 4GB was actually being used from the installer on root and I had the following:
System information as of Sat Jun 8 15:40:10 UTC 2019
=> / is using 95.7% of 3.87GB
After resizing the /dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.8G 0 100% / I thought I'd try to log in and Voila! I was able to log in again. Not sure if I missed something the night I did the install or what, as previously I had always done up specific partition sizes based off of what I'd read online (e.g. separate root / tmp / home / etc) but this time I went with what everyone recommended was let it do LVM and let it auto populate/adjust. It gave me the full 410GB on the LVM but stuck root at 4gb which had filled up, thus not letting me log in with the GUI (local) nor do any updates/etc.
Figured I would post the solution I found in case anyone else had issues with not being able to log in to the Desktop GUI and turns out it was a full root partition. Thanks all! ~AW
add a comment
|
So here is what I found out. As I was troubleshooting other issues that had shown up (prior to getting on to the routing/NAT issue, I found that I now had no way to even run sudo apt-get update, as I was getting all sorts of 'Failed to write, drive full' errors).
Long story short, apparently even though I have a 410G raid set up on the server and had partitioned it with LVM upon the original install, only 4GB was actually being used from the installer on root and I had the following:
System information as of Sat Jun 8 15:40:10 UTC 2019
=> / is using 95.7% of 3.87GB
After resizing the /dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.8G 0 100% / I thought I'd try to log in and Voila! I was able to log in again. Not sure if I missed something the night I did the install or what, as previously I had always done up specific partition sizes based off of what I'd read online (e.g. separate root / tmp / home / etc) but this time I went with what everyone recommended was let it do LVM and let it auto populate/adjust. It gave me the full 410GB on the LVM but stuck root at 4gb which had filled up, thus not letting me log in with the GUI (local) nor do any updates/etc.
Figured I would post the solution I found in case anyone else had issues with not being able to log in to the Desktop GUI and turns out it was a full root partition. Thanks all! ~AW
add a comment
|
So here is what I found out. As I was troubleshooting other issues that had shown up (prior to getting on to the routing/NAT issue, I found that I now had no way to even run sudo apt-get update, as I was getting all sorts of 'Failed to write, drive full' errors).
Long story short, apparently even though I have a 410G raid set up on the server and had partitioned it with LVM upon the original install, only 4GB was actually being used from the installer on root and I had the following:
System information as of Sat Jun 8 15:40:10 UTC 2019
=> / is using 95.7% of 3.87GB
After resizing the /dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.8G 0 100% / I thought I'd try to log in and Voila! I was able to log in again. Not sure if I missed something the night I did the install or what, as previously I had always done up specific partition sizes based off of what I'd read online (e.g. separate root / tmp / home / etc) but this time I went with what everyone recommended was let it do LVM and let it auto populate/adjust. It gave me the full 410GB on the LVM but stuck root at 4gb which had filled up, thus not letting me log in with the GUI (local) nor do any updates/etc.
Figured I would post the solution I found in case anyone else had issues with not being able to log in to the Desktop GUI and turns out it was a full root partition. Thanks all! ~AW
So here is what I found out. As I was troubleshooting other issues that had shown up (prior to getting on to the routing/NAT issue, I found that I now had no way to even run sudo apt-get update, as I was getting all sorts of 'Failed to write, drive full' errors).
Long story short, apparently even though I have a 410G raid set up on the server and had partitioned it with LVM upon the original install, only 4GB was actually being used from the installer on root and I had the following:
System information as of Sat Jun 8 15:40:10 UTC 2019
=> / is using 95.7% of 3.87GB
After resizing the /dev/mapper/ubuntu--vg-ubuntu--lv 3.9G 3.8G 0 100% / I thought I'd try to log in and Voila! I was able to log in again. Not sure if I missed something the night I did the install or what, as previously I had always done up specific partition sizes based off of what I'd read online (e.g. separate root / tmp / home / etc) but this time I went with what everyone recommended was let it do LVM and let it auto populate/adjust. It gave me the full 410GB on the LVM but stuck root at 4gb which had filled up, thus not letting me log in with the GUI (local) nor do any updates/etc.
Figured I would post the solution I found in case anyone else had issues with not being able to log in to the Desktop GUI and turns out it was a full root partition. Thanks all! ~AW
answered Jun 8 at 19:29
user99056user99056
311 silver badge4 bronze badges
311 silver badge4 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1149644%2f18-04-server-can-log-in-remote-but-not-local%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown